fix: add __call__ to MockOptional for WTForms validator compatibility#63823
Open
YoannAbriel wants to merge 1 commit intoapache:mainfrom
Open
fix: add __call__ to MockOptional for WTForms validator compatibility#63823YoannAbriel wants to merge 1 commit intoapache:mainfrom
YoannAbriel wants to merge 1 commit intoapache:mainfrom
Conversation
d7f91de to
25f7029
Compare
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
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.
HookMetaService.MockOptionallacks a__call__method. When FAB initializes WTForms forms duringPOST /auth/token, storedMockOptionalinstances failcheck_validatorsbecause they're not callable — every token request returns 500.Added
__call__(self, form, field)as a no-op soMockOptionalsatisfies the WTForms validator protocol. Added unit tests.Closes: #63803
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4, claude-opus-4-6) following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.