-
Notifications
You must be signed in to change notification settings - Fork 0
fix: Fix usage of register entity type URL #786
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
kingston
merged 5 commits into
main
from
kingston/eng-937-centralize-registerentitytypeurl-to-single-file
Feb 26, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d669461
refactor: Refactor entity type URL registration to use a plugin spec …
kingston c289de9
Support grandparent schemas
kingston 3134a83
Clean up project definition calls
kingston 2187463
Fix up ref dialog
kingston f190c1d
Fix knip
kingston File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| --- | ||
| '@baseplate-dev/project-builder-lib': patch | ||
| '@baseplate-dev/project-builder-web': patch | ||
| --- | ||
|
|
||
| Refactor entity type URL registration to use a plugin spec with a typed discriminated union navigation target system. Builders now register via `entityTypeUrlWebSpec.register(entityType, builder)` with params typed based on whether the entity has a parent — `parentId` and `parentKey` are required strings for child entity types and `undefined` for root entity types. |
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Keep
parserContext.pluginStoreconsistent withpluginStoreinside the container.Both factories pass an updated
pluginStore(Lines 147/169) but still pass the originalcontext(Lines 145/168). This can leavethis.parserContext.pluginStoreout of sync withthis.pluginStore.Suggested fix
static fromDefinition( definition: ProjectDefinition, context: SchemaParserContext, ): ProjectDefinitionContainer { const { definition: parsedDefinition, pluginStore } = parseProjectDefinitionWithReferences(definition, context); const schema = createProjectDefinitionSchema( createDefinitionSchemaParserContext({ plugins: pluginStore }), ); + const parserContext: SchemaParserContext = { + ...context, + pluginStore, + }; return new ProjectDefinitionContainer( parsedDefinition, - context, + parserContext, pluginStore, schema, ); } @@ static fromSerializedConfig( config: unknown, context: SchemaParserContext, ): ProjectDefinitionContainer { const plugins = createPluginSpecStore(context.pluginStore, config); const schema = createProjectDefinitionSchema( createDefinitionSchemaParserContext({ plugins }), ); + const parserContext: SchemaParserContext = { + ...context, + pluginStore: plugins, + }; return new ProjectDefinitionContainer( deserializeSchemaWithTransformedReferences(schema, config), - context, + parserContext, plugins, schema, ); }Also applies to: 166-170
🤖 Prompt for AI Agents