Remove default properties before generating the config types #5126
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.
📑 Summary
Currently, some configuration types listed in
packages/mermaid/src/config.type.ts
appear duplicated (such asXYChartAxisConfig1
andXYChartAxisConfig2
). This is caused by an issue on thejson-schema-to-typescript
package.This PR addresses the effect of that third-party issue on the generated types.
Resolves #5125
📏 Design Decisions
I added a small routine that recursively removes a given property from the loaded JSON schema. It gets called before generating the TypeScript types, in order to remove the
default
property. This does not affect the default values loaded at run-time, since those values are obtained through the.vite/jsonSchemaPlugin.ts
script.📋 Tasks
Make sure you
MERMAID_RELEASE_VERSION
is used for all new features.develop
branch