razorpay / razorpay/razorpay-node
[Feature]: More responsiveness from maintainers. Maybe take help of contributors?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 243
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
🚀 Feature Proposal
This library uses the requests library which is deprecated. This was first reported in #166 in 2020! No action has been taken by maintainers till date!
Also, support for es modules is necessary #350.
@gaganbiswas already has done some work towards both of these in #397 but no activity from the maintainers is seen on that matter!
Suggested Solution
If the maintainers do not possess deep expertise in technical matters, they could take assistance from helpful community members. If they do not have enough time available, again community can help. But somehow we must ensure
that Razorpay Node SDK becomes and remains a high-quality client library reflective of Razorpay's commitment to excellence.
Alternatives
No response
Additional Information
No disrespect to the maintainers.
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
Review the prior reports in #166 and #350 and the community work in #397 before choosing a concrete scope. The issue does not identify files, tests, or a single change, so completion criteria would need to be established for the requests-library replacement and ES module support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100