API Enrichment: add ability to mark fields as missing #908
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
Currently we are very strict about building inputs. When a single value is missing it is no longer possible to use the existing inputs. This backwards-compatible feature adds ability to mark fields as allowed to be missing.
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.
Previously it was impossible to send API enrichment request when any configured input was missing.
Now it is possible to set an additional new
allowMissingflag. Setting the parameter totrueskips the input as optional and sends API request with only the required inputs as well as other available optional fields.Similarly to previous behaviour when no inputs were configured and the request was sent with empty input when no
allowMissingfields are found the request is sent as empty.Part of PDP-1641