You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am looking to start using this plugin, however I'm a bit confused about what I should do with my existing use of @backstage/plugin-entity-validation.
The (official?) plugin seems to make a request to the catalog API for entity validation. I assume this allows for some sort of customization on entity validation by the backstage implementers?
The text was updated successfully, but these errors were encountered:
One other big difference is that plugin uses @uiw/react-codemirror which stylistically looks vert different than all the other tools. Do you see that being a problem, or would you consider porting the default editor here to use codemirror?
Just another note, I tried doing the simple thing of just passing <EntityValidationPage /> as a tool in the toolbox extraTools config. This rendered the tool in the UI, but the validate button wasn't working and causing some errors.
For now, I just added a link button on that custom page to the deployed validation page at "/entity-validation"
I am looking to start using this plugin, however I'm a bit confused about what I should do with my existing use of
@backstage/plugin-entity-validation
.I see the implementation here does not follow the same approach in @backstage/plugin-entity-validation.
The (official?) plugin seems to make a request to the catalog API for entity validation. I assume this allows for some sort of customization on entity validation by the backstage implementers?
The text was updated successfully, but these errors were encountered: