Skip to content

einride/backstage-go vs tdabasinskas/go-backstage #17

@tdabasinskas

Description

@tdabasinskas

Hey!

As the other of tdabasinskas/go-backstage, I'm thinking if we are not introducing additional confusion between the users on which library they should use, as well as duplicating the effort on both sides growing these libraries.

Just curious, have you considered contributing to or forking tdabasinskas/go-backstage instead when starting development of this from scratch? The CLI part is quite nice and useful, but maybe it could have been built on the mentioned SDK?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions