feat(lexicon): validate value on set #57828
Open
+44
−10
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
6d760bc to
a9488d7
Compare
a9488d7 to
8efae41
Compare
provokateurin
requested changes
Jan 27, 2026
come-nc
reviewed
Jan 27, 2026
8efae41 to
c44bb57
Compare
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
c44bb57 to
d52b218
Compare
Member
Author
|
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.
Adding a new parameter to Lexicon
Entryso that aClosurecan be set to validate the config value before storing it to database.This would allow to use
provision_apiendpoints to set app/user configs while keeping an eye on its value without having a specific controller.would be nice to have this added to next RC of 33, as it could be used to confirm the format of a string when configuring Federated Teams