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

Add clarifications about the presence and lack of data schemas #2028

Open
egekorkan opened this issue Jun 17, 2024 · 0 comments
Open

Add clarifications about the presence and lack of data schemas #2028

egekorkan opened this issue Jun 17, 2024 · 0 comments
Labels
Data Schema Editorial Issues with no technical impact on implementations useful-documentation good for documentation purposes later on

Comments

@egekorkan
Copy link
Contributor

We are clear what happens if a data schema, let's say input of actions, exist in a TD or if they don't. For all cases, we should explain the expected behavior when they exist, do not exist or when they are empty (i.e. "input":{}). It should be also clear that these are not optional if the Thing expects the data schema, i.e. input should exist if Thing expects an input payload.

@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Jun 17, 2024
@egekorkan egekorkan added Editorial Issues with no technical impact on implementations useful-documentation good for documentation purposes later on Data Schema and removed needs-triage Automatically added to new issues. TF should triage them with proper labels labels Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Schema Editorial Issues with no technical impact on implementations useful-documentation good for documentation purposes later on
Projects
None yet
Development

No branches or pull requests

1 participant