As in Node-RED we have some guidelines for the JWT contribution package. We welcome contributions, but request you follow these guidelines.
- Code for one another, and use tools to perform mechanical optimizations.
- Keep it simple; compactness != succinctness.
- Just because you can doesn’t mean you should.
- Utilize familiar paradigms and patterns.
- Consistency is king.
- Lay good foundations. Be mindful of evolutionary complexity.
Please raise any bug reports on the relevant project's issue tracker. Be sure to search the list to see if your issue has already been raised.
A good bug report is one that make it easy for us to understand what you were trying to do and what went wrong.
Provide as much context as possible so we can try to recreate the issue. If possible, include the relevant part of your flow. To do this, select the relevant nodes, press Ctrl-E and copy the flow data from the Export dialog.
At a minimum, please include:
-
Version of node.js? (should be >= 16)
-
Version of Node-RED? (should be >= 3)
-
Version of node-red-contrib-bit? (should be >= 1)
-
What is your platform? (Linux, macOS, ...)
-
What does
DEBUG=* node-red -v
log? (log files are welcome)
For feature requests, please raise them on the relevant project's issue tracker.
If you want to raise a pull-request with a new feature, or a refactoring of existing code, it may well get rejected if you haven't discussed it on the relevant project's issue tracker first.
Please ensure you follow the coding standards used through-out the existing code base.
Some basic rules include:
- all files must have the MIT license in the header.
- indent with 2-spaces, no tabs. No arguments.
- follow ES6 or above coding standards
- follow standard.js coding standards
Please, make pull requests! If you are not sure how to do this, then ask for help please! It is open source to collaborate and to give some return of investment with your code.