oasisprotocol / oasisprotocol/oasis-sdk
ts-web: Remove some elements that won't be used
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 90
- Forks
- 35
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 5
Description
An example, common.CODE_CERTIFICATE_ROTATION_FORBIDDEN:
The identity module is not exposed to clients so it probably doesn't make much sense to transfer it over?
Originally posted by @kostko in https://github.com/oasisprotocol/oasis-sdk/pull/4#discussion_r580102438
currently we've transferred a pretty broad set of methods, constants, etc., mostly by scanning the Go codebase for certain types and registration calls. let's come up with a more sophisticated way choosing what to model and what not to model in the typescript SDK
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ts-web entry point and the Go codebase scanning and registration flow described in the issue. Identify how methods and constants are currently selected, then define the client-facing scope for modeled elements; done means the TypeScript SDK excludes elements that are not exposed to clients and follows the agreed selection rules.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, typescript
- Domain
- api, blockchain, developer-experience
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100