It's quite typical for a bug report to only state in vague / high level terms
what is wrong. If you are lucky, it also describes the expected behavior. If you
are unlucky, it tells you exactly, but wrongly, what to do.
Finding out what code you need to touch to fix the issue is the programmer's
job. Coming up with a good way to fix it is the programmer's job. Defining the
specification is also the programmer's job (ideally, in form of a unit test).
Actually *writing* the code is often the easiest part.
Finding the right play and a good way is of course very hard at first - you will
need to ask people to help you to find the right spot in the code. In case of
the ticket you mention, you could try to find someone who is familiar with the
extension in querstion, and ask them where the code is that generates the JSON
Am 13.10.2014 11:33, schrieb Alisha Jain:
I am trying to work on this work to apply for FOSS
opw. I have gone
through the comments and understood the code regarding this bug. But I
am not getting what is the bug in the code? What are the requirements?
I want to see the bug in action. So please guide me so that I can