jsantell / jsantell/node-cfx

add deprecation notices

Open
#10 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Description

I created a deprecation branch (diff) as a proposal for the changes (first time being on a project w/ multiple contributers on github).

Should we also add messages when ran by users? (e.g. console.warn(...);?)

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 reviewing the deprecation branch and its linked comparison diff to understand which changes are proposed. Resolve whether user-facing deprecation messages are required, then verify that the agreed notices appear when the affected commands are run.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.