James Pang

@eugenepeh @fzdy1914 is it okay for us to have a more robust set of front end tests? This is so that we can better prevent the front end regressions. However,...

@Tejas2805 it may be better to focus on other issues as this issue may not be as critical.

Update: realise that some parts of the code uses ES6 string interpolation but some don't, let's standardise it. https://github.com/reposense/RepoSense/blob/61f1fc4f4f854a176ab1f6672f6759c42712c9c3/frontend/src/ramp.pug#L10

> Your POV on this? Hmm my view on we should only convert it when it will improve the readability/efficiency.

@damithc Should we impose a limit on the number of lines we can display per file? e.g. if the number of lines of a file has > 5000 lines, we...

Hmm there might still be cases where the commits contain extremely large files as below and loading them as a single file might still not be feasible: Going to the...

> ``` > git fetch --all && git config --global user.email "-" && git config --global user.name "-" > && ./gradlew clean build && ./gradlew run -Dargs="--since d1" > ```...

@eugenepeh don't think its due to `./gradlew run` but its due to `./gradlew clean build`

@eugenepeh I think the dependency `'com.github.javaparser', name: 'javaparser-core', version: '3.0.1'` seems to be redundant as in PR [here](https://github.com/reposense/RepoSense/commit/ec45509189bf4a07654e16b2466ad7fedb1d56bc) decided to use `'net.sourceforge.argparse4j'` for the parsing functionalities. Have run the without...

> @eugenepeh I think the dependency `'com.github.javaparser', name: 'javaparser-core', version: '3.0.1'` seems to be redundant as in PR [here](https://github.com/reposense/RepoSense/commit/ec45509189bf4a07654e16b2466ad7fedb1d56bc) uses `'net.sourceforge.argparse4j'` for the parsing functionalities. @yong24s May I get your...