w3c / w3c/wot-scripting-api

writeMultipleProperties() method misses op writeallproperties

Open
#362 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API-improvement for next iteration priority: high wait-for-td
Dominant language
HTML
Stars
45
Forks
21
PR merge metrics
No merged PRs in 30d

Description

The writeMultipleProperties() method states in Step 3

If option's formIndex is defined, let form be the Form associated with formIndex in [[td]]'s forms array, otherwise let form be a Form in [[td]]'s forms array whose op is writemultipleproperties, selected by the implementation.

Should we also op writeallproperties ?

relates to https://github.com/w3c/wot-scripting-api/issues/219

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the writeMultipleProperties() method and Step 3 in the linked WoT Scripting API specification, then review related issue #219. Determine whether the form selection should also allow the writeallproperties operation; the issue is done when the specification wording and related issue are resolved consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.