Vincenzo Scamporlino
Vincenzo Scamporlino
did #30390 fix the issue @madsteer?
now I see it, thanks for sharing this @dotboris 🙏 We could remove the deprecated option and clarify this use case in the documentation. Otherwise another option I see is...
cc @kurtaking
Closing this issue for now that #5970 has landed
yep, ideally the fields should be updated depending on the columns that are rendered
hey this is great @rothenbergt 🙏 I'm thinking it would be nice to describe the development process in the README!
just some conflicts to be resolved and then we can ship this!
> Interesting to know that by design, you should only register locations on default branches I think the suggestion is to avoid registering entities on temporary branches that get renamed/deleted/merged....
Just so you know this doesn't depend on where the location is stored. Make sure you are hitting the right endpoint: (I see a missing `/api` in your example) `/api/catalog/locations/by-entity/{kind}/{namespace}/{name}`....