You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The JSON Schema community is a welcoming group of practitioners and experts who would love to help peers, but in order to improve your chances of getting an answer, here are some tips:
Research before posting.
Before posting a question, we recommend that you spend a reasonable amount of time researching the problem and searching for existing community discussions that may provide an answer.
Tell the community what you found in your research and why it didn't meet your needs. This demonstrates that you've taken the time to try to help yourself, it saves others' time from reiterating obvious answers, and above all, it helps you get a more specific and relevant answer!
Introduce the problem before posting any code.
In the body of your question, start by expanding on the summary you put in the title. Take your time with the code! It is often helpful to provide some background contextual information, and describing your problem in words is almost as important as describing it with code.
Explain how you encountered the problem you're trying to solve and any difficulties that have prevented you from solving it yourself.
Help others reproduce the problem.
Not all questions benefit from including code, but if your problem is with the code you've written, you should include some. But don't just copy in your entire program!
Here are some guidelines:
Include just enough code to allow others to reproduce the problem.
Add a live example of the problem when that is possible.
DO NOT post images of code, data, error messages, etc.—copy or type the text into the question. Please reserve the use of images for diagrams or demonstrating rendering bugs, things that are impossible to describe accurately via text.
Respond to feedback after posting.
If someone posts an answer, be ready to try it out and provide feedback! Sometimes, you may find yourself frustrated by the comments. They may make suggestions that you have already tried. On the other hand, they may totally misunderstand your problem. Try not to get frustrated—people reading and commenting on your question generally want to help! Take these types of comments as suggestions as an opportunity to get a better answer.
Keep an open mind.
The answer to your question may not always be what you wanted, but that doesn't mean it is wrong. A conclusive answer isn't always possible. When in doubt, ask people to cite their sources, or to explain how/where they learned something. Even if we don't agree with you, or tell you exactly what you wanted to hear, remember: we're just trying to help.
Here are some additional resources that you may find useful:
Sometimes it might be difficult to write your first question, but don't worry this community is here to support you! We hope you might find these tips useful.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
JSON Schema
-
How do I ask a good question?
The JSON Schema community is a welcoming group of practitioners and experts who would love to help peers, but in order to improve your chances of getting an answer, here are some tips:
Research before posting.
Before posting a question, we recommend that you spend a reasonable amount of time researching the problem and searching for existing community discussions that may provide an answer.
Tell the community what you found in your research and why it didn't meet your needs. This demonstrates that you've taken the time to try to help yourself, it saves others' time from reiterating obvious answers, and above all, it helps you get a more specific and relevant answer!
Introduce the problem before posting any code.
In the body of your question, start by expanding on the summary you put in the title. Take your time with the code! It is often helpful to provide some background contextual information, and describing your problem in words is almost as important as describing it with code.
Explain how you encountered the problem you're trying to solve and any difficulties that have prevented you from solving it yourself.
Help others reproduce the problem.
Not all questions benefit from including code, but if your problem is with the code you've written, you should include some. But don't just copy in your entire program!
Here are some guidelines:
Respond to feedback after posting.
If someone posts an answer, be ready to try it out and provide feedback! Sometimes, you may find yourself frustrated by the comments. They may make suggestions that you have already tried. On the other hand, they may totally misunderstand your problem. Try not to get frustrated—people reading and commenting on your question generally want to help! Take these types of comments as suggestions as an opportunity to get a better answer.
Keep an open mind.
The answer to your question may not always be what you wanted, but that doesn't mean it is wrong. A conclusive answer isn't always possible. When in doubt, ask people to cite their sources, or to explain how/where they learned something. Even if we don't agree with you, or tell you exactly what you wanted to hear, remember: we're just trying to help.
Here are some additional resources that you may find useful:
Sometimes it might be difficult to write your first question, but don't worry this community is here to support you! We hope you might find these tips useful.
Thank you!
Credits:
Beta Was this translation helpful? Give feedback.
All reactions