Merged
Conversation
Signed-off-by: Christian Biasuzzi <christian.biasuzzi@soft.it>
flo-dup
force-pushed
the
nad_enrich_metadata_custom_style
branch
from
9da5589 to
d0c3c52
Compare
flo-dup
previously approved these changes
Mar 30, 2026
Signed-off-by: Christian Biasuzzi <christian.biasuzzi@soft.it>
|
flo-dup
approved these changes
Mar 30, 2026
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
2 participants
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
This PR is built on top of PR #781 (which addresses issue #762)
What kind of change does this PR introduce?
feature: adds inline style, as created by the CustomStyleProvider, to the json metadata.
For name consistency, it additionally renames styleClass to style (in some model classes attributes and methods).
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: