CyberSource / CyberSource/cybersource-rest-client-node

Please start using SemVer

Open
#68 2 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
49
Forks
50
Avg merge
18m
Merged PRs (30d)
2

Description

This library introduces major changes to its API in seemingly minor version updates.

Eg. Previously generatePublicKey introduced a new parameter (format) a while ago and somehow it was decided to add it as first parameter, breaking existing calls to it

Now in between 0.0.28 and 0.0.29 there was a fatal deprecation of the RunEnvironment config settings which again, breaks the API calls.

Can you please start using SemVer (https://semver.org/) for this library to flag breaking changes appropriately?

Contributor guide

No contributing guide indexed for this repository

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 by reading the linked semver.org guidance and reviewing this library's release and versioning process. Define how breaking API changes such as generatePublicKey and RunEnvironment deprecation should be versioned, and consider the work complete when future releases consistently signal compatibility changes according to SemVer.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.