Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for validating intent params #145

Open
danielwiehl opened this issue Apr 29, 2022 · 1 comment
Open

Support for validating intent params #145

danielwiehl opened this issue Apr 29, 2022 · 1 comment
Labels
Projects

Comments

@danielwiehl
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Parameters that are passed along with intents can be marked as required, but no expected data type can be specified. Thus, on the provider side, it must always be checked whether the passed parameters satisfy the requirements.

Describe the solution you'd like

The platform should support the declaration of the expected data type for parameters. It should be possible to specify a JSON schema inline in the parameter definition or to reference an existing JSON schema.

I can imagine registering JSON schemas as capabilities that can be referenced in both parameter definitions and message payload validation. The platform should provide default JSON schema capabilities for primitive data types such as string, number, and boolean.

@danielwiehl danielwiehl added this to Triage in SCION via automation Apr 29, 2022
@danielwiehl danielwiehl moved this from Triage to Backlog Microfrontend Platform in SCION Apr 29, 2022
@danielwiehl
Copy link
Collaborator Author

See related issue #144.

@danielwiehl danielwiehl changed the title Validate intent params as needed Support for validating intent params Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
SCION
  
Backlog Microfrontend Platform
Development

No branches or pull requests

1 participant