- Start logging an issue in the issue tracker.
- Clearly identify the problem and submit some reproduction code.
- Prune the reproduction to remove needless details.
- State the current and expected behaviour.
- State the version of ts-nameof (always show a reproduction of the bug on the latest version).
- Follow the instructions above about logging a bug. In addition:
- State that you are going to work on the bug.
- Discuss major structural changes in the issue before doing the work to ensure it makes sense and work isn't wasted.
- Start working on the fix in a branch and submit a PR when done.
- Ensure
yarn verifypasses when run in the root directory.
- Log an issue in the issue tracker. In the issue:
- Propose the change.
- Outline all changes that will be made to the public API.
- Discuss any structural changes to the code if necessary.
- Wait for discussion and green light from @dsherret (who will try to reply as soon as possible, but it might take a few days).
- Note: If the change is small and you think it wouldn't take you too much time, then feel free to start working on it and even submit a PR. Just beware that you're taking the risk that it could be denied.
- Propose the change.
- After approval, start working on the change in a branch and submit a PR.
- Read DEVELOPMENT.md for some useful information.
- Ensure
yarn verifypasses when run in the root directory.