We’d love to help you. To improve your chances of getting an answer, here are some tips:
... and keep track of what you did. Even if you don't find a useful answer, including links to documentation or similar questions that gave you a clue can help us understand your approach.
The title is the first thing we see and will set the tone for everything that comes after. So make it count.
- Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem?
- Spelling, grammar and punctuation are important!
- If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem.
Examples:
- Bad: Broken loop
- Good: My counter variable isn't incrementing during a while loop
- Bad: if else problems
- Good: Why does arr === ["Hello World!"] evaluate to false when arr is set to ["Hello World!"]?
In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself.