Damith C. Rajapakse

The current priority order is a bit odd. How about this? The normal priority order CLI > report config > standalone config This means report config files will override standalone...

sounds good. We can change `--ignore-standalone-config` to `--apply-standalone-config`/`-a` to mean _apply_ standalone config. What do you think?

> The order is better, however, wouldn't this means that if I were want to ignore a specific field in standalone config, I will need to fill up all the...

> For this `apply`, do you mean that the rest field in standalone config can be used or the field can override the value in CLI? It can mean _the...

We'd better define all possibilities. * `--inherit` * standalone missing, csv present: * standalone present, csv missing: * both absent: * both missing: * default * standalone missing, csv present:...

Sounds good. Minor change given below. `--inherit` * both present: use CSV values, empty fields will be obtained from standalone config. **use `""` in csv file to use default instead...

> on visible rendering might prevent searching the page using ctrl-f > > Possible worse experience as users may need to wait for entries to render while scrolling Alternative: render...

Looks like the bot auto-closed this. Should it be closed?

> However, since modal is quite a departure from the current design, for this issue, I would like to address it in a way that when a viewer hovers on...

> Is there a way to verify whether the page size has increased? > Is looking at the file size for `index.html` under `reposense-report` directory a correct way to verify...