einride / backstage-go Goto Github PK

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?

Hello @odsod! I see you are the owner of this repo. I was wondering if you are currently accepting PR for new features? I was looking at adding a new field here, https://pkg.go.dev/go.einride.tech/backstage/catalog#EntityRelation that would expose the target. I.E

        "type": "consumesApi",
        "targetRef": "component:default/artist-lookup",
        "target": {
          "kind": "component",
          "namespace": "default",
          "name": "artist-lookup"
        }
      }