The following is a set of guidelines for contributing to Ant Design Mobile. Please spend several minutes in reading these guidelines before you create an issue or pull request.
Anyway, these are just guidelines, not rules, use your best judgment and feel free to propose changes to this document in a pull request.
It's a great idea to read Eric Steven Raymond's How To Ask Questions The Smart Way twice before asking a question. But if you are busy now, I recommend to read Don't post homework questions first.
The following guidelines are about How to avoid Homework Questions.
It sad but true that someone just glance(not read) Ant Design Mobile's documentation. Please read the documentation closely.
Tips: choose the corresponding documentation with versions selector which in the bottom-right corner.
Someone may think all of the questions that he/she meets in developing are about Ant Design Mobile, but it's not true. So, please read React's documentaion or just Google(not Baidu, seriously) your questions with keywork React first. If you are sure that your question is about Ant Design Mobile, go ahead.
Your questions may be asked and solved by others. So please spend several minutes on searching. Remember DRY, both code and questions.
P.S.
It is a good habit which will save maintainers' time. Thank you!
It would be helpful to provide a demo which can re-produce the bug 100%. Please give us the steps in detail that can help us re-producing the bug you met. Then, create an issue. The most important thing is: double check before claiming that you have found a bug.
If you believe that Ant Design Mobile should provide some features, but it does not. You could create an issue to discuss. However, Ant Design Mobile is not Swiss Army Knife, there are some features which Ant Design Mobile will not support:
- Request or operate data
It's welcomed to pull request. And there are some tips about that:
- It is a good habit to create a feature request issue to disscuss whether the feature is necessary before you implement it. However, it's unnecessary to create an issue to claim that you found a typo or improved the readability of documentaion, just create a pull request.
- Run
npm run lint
and fix those errors before committing in order to keep consistent code style. - Rebase before creating a PR to keep commit history clear.
- Add some descriptions and refer relative issues for you PR.