[GR-39852] [GR-40423] Provide FieldValueTransformer API. #4820
Conversation
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
oracle-contributor-agreement
bot
added
the
OCA Verified
graalvmbot
force-pushed
the
cwi/GR-39852-FieldValueTransformer
branch
2 times, most recently
from
cc4e3b3 to
8d61e31
Compare
graalvmbot
force-pushed
the
cwi/GR-39852-FieldValueTransformer
branch
from
8d61e31 to
837030b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See the JavaDoc of the new class
FieldValueTransformerfor the API description.FieldValueTransformerreplaces theCustomFieldValueProvider/CustomFieldValueComputer/CustomFieldValueTransformerthat we had inRecomputeValueFieldfor the kindCustom. But more importantly from an API point of view, the transformer can now also be registered from aFeature, i.e., without the need to use the substitution mechanism.For simplicity, the actual implementation of transformations did not change. It is still done via the substitution universe, i.e, the field value transformer are still invoked from
ComputedValueField. This PR also does not remove existingRecomputeFieldValueannotations in our code base.