Closed nuritizra closed 1 month ago
@punkle @karlhaworth appreciate your review!
Could we at the same time modify the naming convention in exporting the plugin. It looks very unprofessional to be exporting alpha
functionality and I'm not sure if that's worth doing. Is the frontend system finalized at this stage?
@Xantier the frontend system is not stable yet and there will be more breaking changes. Whether you want to have it exported via /alpha
or not is up to you tbh, but you'd ofc need to make sure you forward any breaking changes from the core APIs that affect the external API of your package.
Hmm, thanks @Rugvip. @nuritizra would it make sense to hold off on this until the frontend system gets into a stabler state. Currently this addition looks to be just introducing a maintenance burden.
This PR has been automatically marked as stale because it has not had recent activity from the author. It will be closed if no further activity occurs. If the PR was closed and you want it re-opened, let us know and we'll re-open the PR so that you can continue the contribution!
@Xantier these changes are just helping out with the migrations from https://backstage.io/docs/frontend-system/architecture/migrations#130. We want to push for adoption of the new frontend system by plugins already now, because it's hard to move to and encourage adoption in apps until we have decent support from plugins.
Thanks @Rugvip, wouldn't it be better to wait for few adopters who are using the frontend system on their instances before we start adding these in. It is quite a burden to keep these up to date with alpha version of the framework since there are changes expected on the underlying interfaces.
Would you be maintaining this migration @nuritizra ?
Added some fixes while the docs were updated to use blueprints. Also, we don't need the page extension as we only use cards. In addition, I updated the README file.
:heavy_check_mark: Checklist
yarn changeset
in the root)