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.

Sign up for GitHub

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

Jump to bottom

Follow-up on validating output for (async) actions #1290

Open
danielpeintner opened this issue Jun 7, 2024 · 0 comments
Open

Follow-up on validating output for (async) actions #1290

danielpeintner opened this issue Jun 7, 2024 · 0 comments
Labels
core Issues with the core library enhancement New feature or request need-investigation

Comments

@danielpeintner
Copy link
Member

danielpeintner commented Jun 7, 2024 •
edited
Loading

Given the discussion of today's committer meeting:

  • TD spec is not clear about what to expect when the sync property is missing
  • Eargerly validate the output in this cases means to try out smart the developer which is quite a bad practice
  • Therefore we decided to merge this PR as a workaround for the whole situation. We acknowledge that there needs to be follow up fixes both in Scripting API and Thing Description spec to properly solve the issue.

Originally posted by @relu91 in #1279 (review)

See also Scripting API issues w3c/wot-scripting-api#554 and w3c/wot-scripting-api#555
@relu91 relu91 added enhancement New feature or request core Issues with the core library need-investigation labels Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core Issues with the core library enhancement New feature or request need-investigation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@relu91 @danielpeintner