Workaround date picker in date form field #8
Conversation
This file contains 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.
Date Form field picker workaround
The original issue was that the Android code only checked for a specific action in the formfields to recognize if it’s a date or time field. Turned out that the test document doesn’t have this specfic action set but a different one. Our upcoming patch release will fix this and check for the other action too.
We added a helper class that migrates the formfieds so the SDK recognizes date/time fields correctly (without the patch).
It just needs to be called from the onDocumentLoadedCallback like this:
FormFieldMigrationHelper.migrateFieldFormatActions(document).