From 26ca35f8b466a9ddc4bf4c6b2cb977528374d507 Mon Sep 17 00:00:00 2001 From: Dmitriy Fishman Date: Thu, 25 Nov 2021 15:10:12 +0200 Subject: [PATCH] Update contributing.md (#9893) --- docs/developers/contributing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developers/contributing.md b/docs/developers/contributing.md index e4f479dda..fe0cadbfc 100644 --- a/docs/developers/contributing.md +++ b/docs/developers/contributing.md @@ -6,7 +6,7 @@ New contributions to the library are welcome, but we ask that you please follow - Consider whether your changes are useful for all users, or if creating a Chart.js [plugin](plugins.md) would be more appropriate. - Check that your code will pass tests and `eslint` code standards. `npm test` will run both the linter and tests for you. - Add unit tests and document new functionality (in the `test/` and `docs/` directories respectively). -- Avoid breaking changes unless there is an upcoming major release, which are infrequent. We encourage people to write plugins for most new advanced features, and care a lot about backwards compatibility. +- Avoid breaking changes unless there is an upcoming major release, which is infrequent. We encourage people to write plugins for most new advanced features, and care a lot about backwards compatibility. - We strongly prefer new methods to be added as private whenever possible. A method can be made private either by making a top-level `function` outside of a class or by prefixing it with `_` and adding `@private` JSDoc if inside a class. Public APIs take considerable time to review and become locked once implemented as we have limited ability to change them without breaking backwards compatibility. Private APIs allow the flexibility to address unforeseen cases. ## Joining the project -- 2.47.2