Manage null value for some fields #1170
Merged
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
dtrucs
force-pushed
the
Manage-null-value-for-some-fields
branch
from
fa8c17d to
5cfc2f8
Compare
|
Thanks @dtrucs! I have created an issue on geotrek-admin: GeotrekCE/Geotrek-admin#4192. So hopefully we will be able to fix the root cause. |
Bo-Duke
approved these changes
Jun 19, 2024
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.
The following fields are defined as "string" type in Geotrek-Admin:
But some parsers may set them to
nullon import.We therefore manage these fields in case they return null instead of a string.
cc @marcantoinedupre