27

Basically, the other day, I asked a question on Stack Overflow about an unusual behaviour when coding in TypeScript using Angular.

After a few days of searching deeper, I realised the problem came from Angular itself, so I decided to self-answer my question, by giving the steps to reproduce (and the steps to make it work), after which I went on GitHub and opened an issue on the Angular/Angular CLI project.

Should I include the links to the opened issues in my answer, or isn't it necessary?

2
  • 17
    It's up to you. Links to official or non-official resources which improve your answer are generally appreciated. I'd say the link to the github issue is likely helpful here. Commented Oct 28, 2018 at 18:41
  • Any information that add's to the answer should be included, you want the answer to be as detailed as possible to give it the best chance of helping others. Commented Oct 30, 2018 at 7:48

1 Answer 1

Reset to default
42

Yes, add a link to the official issue tracking. Make sure the answer itself contains enough information about the issue and not just a link-only post, "see official issue 12345".

In addition to providing more information this will let other people to maintain the Q/A pair in the future. If the issue is eventually resolved anyone else can see that and update/add an answer with "Issue fixed in version X.Y.Z. You need to ... ".

1
  • 6
    And for Apple-related issues, please link to an openradar.appspot.com, which is UNofficial, but is the only public way to link to Apple issues. Commented Oct 29, 2018 at 7:15

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.