Skip to content

Latest commit

 

History

History
72 lines (44 loc) · 3.15 KB

CONTRIBUTING.md

File metadata and controls

72 lines (44 loc) · 3.15 KB
Raw

Contribution Guide

To Publish an issue

Thanks for your advise. Before publishing an issue, please check some components.

1. Search for duplicates

Before publishing an issue, please check whether the duplicated issue exists or not.

2. Did you find a bug?

When you reporting a bug, then please write about those items:

  • What version you're using
  • If possible, give me an isolated way to reproduce the behavior.
  • The behavior your expect to see, and the actual behavior.

3. Do you have a suggestion?

I always welcome your suggestion. When you publishing a suggestion, then please write such items:

  • A description of the problem you're trying to solve.
  • An overview of the suggested solution.
  • Examples of how the suggestion whould work in various places.
    • Code examples showing the expected behavior.

Contributing Code

Test your code

Before sending a pull request, please test your new code. You type the command npm run build &&& npm run test, then compiling your code and test-automation will be all processed.

# COMPILE
npm run build

# DO TEST
npm run test

If you succeeded to compile, but failed to pass the test-automation, then debug the test-automation module. I've configured the .vscode/launch.json. You just run the VSCode and click the Start Debugging button or press F5 key. By the debugging, find the reason why the test is failed and fix it.

Adding a Test

As this nestia is not a typical library who being used by the import statement but a executable program generating the SDK (Software Development Kit), adding a test means that adding a demonstration project.

I know that adding a demonstration project is much difficult than adding a test function, but there's no way if newly contributed code requires a new type of testing tool. Looking at the src/test/demonstratios directory and traveling the demonstration projects, create a new demonstration project following their structures and styles.

Of course, if your contribution code does not require a test new project, don't mind this.

Sending a Pull Request

Thanks for your contributing. Before sending a pull request to me, please check those components.

1. Include enough descriptions

When you send a pull request, please include a description, of what your change intends to do, on the content. Title, make it clear and simple such below:

  • Refactor features
  • Fix #17
  • Add tests for #28

2. Include adequate tests

As I've mentioned in the Contributing Code section, your PR should pass the test-automation module. Your PR includes new features that have not being handled in the ordinary test-automation module, then also update add the testing unit please.

If there're some specific reasons that could not pass the test-automation (not error but intended), then please update the ordinary test-automation module or write the reasons on your PR content and const me update the test-automation module.

References

I've referenced contribution guidance of the TypeScript.