feat(endoflife): add new frontend system support - #122
Open
Brezinben wants to merge 1 commit into
Open
Conversation
Adds a `/alpha` entry point exporting the plugin as a `createFrontendPlugin` default export, with an `ApiBlueprint` for the end of life API, an `EntityCardBlueprint` for the card, and an `EntityContentBlueprint` for an optional tab, disabled by default. The existing `/` entry point is unchanged, so apps on the old frontend system are unaffected. Refs dweber019#44
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds new frontend system support to the
endoflifeplugin, via a/alphaentry point. Same dual entry point pattern as #120.Part of #44.
Changes
src/alpha.tsx:ApiBlueprintfor the End of Life API,EntityCardBlueprintfor the card (filtered with the existingisEndOfLifeAvailable), andEntityContentBlueprintfor an optional tab,disabled: trueso apps don't get both surfaces at oncepackage.json:./alphainexports/typesVersions,@backstage/frontend-plugin-apidependencyThe
/entry point is untouched, so old frontend system consumers are unaffected. The existing route ref and API ref work as-is in the new system — no@backstage/core-compat-apiconversion needed.api:endoflifeentity-card:endoflifeentity-content:endoflifeOne deliberate difference from #120
No
exportsblock inpublishConfig.backstage-cli package prepackgenerates the publishedexports,typesVersionsandmoduleitself — including thebackstage.featuresentry and"backstage": "@backstage/FrontendPlugin"export condition that app package discovery needs. Writing it by hand overwrites those, and makesyarn packfail on the next run withExports field value must be a string.Verification
yarn tsc,lint,test(4 suites, 26 tests),prettier:check, andpackall pass. Also installed from a packed tarball into a Backstage 1.53 app on the new frontend system — the card renders its timeline with live data, and a page in that app consumesendOfLifeApiRefthrough theApiBlueprint.🤖 Made with Claude Code.