A suggestion to all gsoc candidates: if you wanna do more contributions to coala before result is announced, I personally recommend you to 1) Solve issues somehow related to your proposed project. E.g. if you are doing a project targeting coala core, it does not quite make sense to show your html/css skills. (They do count, but might not be much). 2) Try to solve difficulty/medium or even difficulty/high issues. Remember, quality is over quantity.
:+1:
@Nosferatul and @RaiVaibhav , I have solved the comment problem in https://github.com/uiri/toml. It may require some changes/polishing and maybe discussion, but the approach will be same. It was the most asked of feature waiting to be resolved for over 2 years. uiri/toml#77
Awsome :+1: But I see uirihas given review on your first PR and you opened a new PR, please don't open new PR, do all changes in one PR, it help in code review
A suggestion to all gsoc candidates: if you wanna do more contributions to coala before result is announced, I personally recommend you to 1) Solve issues somehow related to your proposed project. E.g. if you are doing a project targeting coala core, it does not quite make sense to show your html/css skills. (They do count, but might not be much). 2) Try to solve difficulty/medium or even difficulty/high issues. Remember, quality is over quantity.
:thumbsup:
A suggestion to all gsoc candidates: if you wanna do more contributions to coala before result is announced, I personally recommend you to 1) Solve issues somehow related to your proposed project. E.g. if you are doing a project targeting coala core, it does not quite make sense to show your html/css skills. (They do count, but might not be much). 2) Try to solve difficulty/medium or even difficulty/high issues. Remember, quality is over quantity.
:+1:
