graphql: add destinationTypes
and destinationFieldValidate
queries
#3548
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.
Description:
Implements two new queries for generic destination support. Additionally, a
@experimental
directive was added to mark these fields as experimental in the schema.Run
make start EXPERIMENTAL=dest-types
to start with this feature turned on.Query.destinationTypes
returns a list of all valid/built-in destination types.Query.destinationFieldValidate
can be used to validate the value of a field.Examples:
Valid webhook (returns
true
):Invalid webhook (returns
false
):Which issue(s) this PR fixes:
Part of #2639
Out of Scope:
Describe any introduced user-facing changes:
N/A
Describe any introduced API changes:
Query.destinationTypes
Query.destinationFieldValidate
Additional Info:
A full working implementation of the full suite of API and UI changes is in the
generic-destinations
branch.Note:
generic-destinations
should be considered a POC for the purposes of flushing out the full scope of API changes, the UI code will be cleaned up and merged in pieces with tests.