w3c / w3c/webcrypto

Synchronous API ?

Open
#167 15 comments 7 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
294
Forks
78
PR merge metrics
No merged PRs in 30d

Description

with promise there no way to get synchronous resulte for now...
it means not to have synchronous api in parallel of the asynchronous API?
beceause some time they need synchronous, and some time asynchronous ...

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

The issue names no files, tests, or entry points. Start by reading the issue and its 15-comment discussion to understand the proposed synchronous API and unresolved questions. Done would require a decided scope and an agreed implementation and testing plan.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.