Closed insaynasasin closed 9 years ago
So this PR will fix issue #180. (Mentioning this issue id will create a x-reference between the issue and PR)
i have changed the menu entry and also the corresponding case as you said. is it fine now?
Sorry, but I was a bit stressed out the last two weeks in fixing breakage of our CI systems. So I had lesser time for reviews. So let me have a look at your updated PR now.
I am sorry for not testing. Please tell me after I have made changes to the actual code how would i test it? You mentioned in you comment that you tested it using ant run. So is this ant run used for such testing purposes?
Yes, so in general it is necessary to test the code you have written. At least by doing it manually. Better is to write a test for. That is a bit harder, but always preferred. The existing tests for memchaser you can fine here. Those are low-level unit tests so far. In your case I don't think we can easily handle that, and may be not necessary.
To run the tests you have to use the tool ant. I'm not sure on which system you are working on, but e.g. on Linux it will be pre-installed. It's configuration is done in the build.xml file as located at the root of this repository. It contains all the possible commands incl. test
(running automated tests) and run
(start Firefox for manual testing). So you might want to have to install [ant](http://ant.apache.org/manual/install.html)
.
@insaynasasin do you have time to continue this pull request with addressing @whimboo's comment?
@whimboo, I'd like to continue this PR (ok, not this, but an another, based on this) after the other logging related PRs got merged.
The logging PRs have been merged. So I think we are good to go here?
Sure.
Should I open a new PR, addressing your comments?
Merged to PR #220, comments addressed.
Closing.
added a new link on the content.html page and updated the corresponding action in the main.js file