wechat-miniprogram / wechat-miniprogram/api-typings
No typing definition for wx.serviceMarket
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 803
- Forks
- 117
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Any reason why there is no typing for wx.serviceMarket especially invokeService api?
Different service api require different input/output - it can be easily done via generics.
Any plan to add it in the future?
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 by reviewing the existing TypeScript definitions for wx.serviceMarket and the invokeService API, then compare how other service APIs represent their inputs and outputs. Done means adding agreed generic typings that distinguish the input and output types for different services, with coverage for the relevant API shapes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100