HEdingfield
HEdingfield
Per the discussion in PR #730, let's see if we can expand GitHub Actions to include more of the linting-style checks that IntelliJ does (so our big end-of-release refactoring PRs...
As mentioned in PR #730, let's consider adding a blame layer ignore file to exclude the large refactoring commits from the blame layer. Bonus points if we can set up...
Per [this discussion](https://github.com/BrightSpots/rcv/pull/690#discussion_r1227599481): > the output CSV (should) have the canonical names in one column and then perhaps a separate column that lists any alias that are used for each...
We should document our IntelliJ setup, which plugins we use, how to use Gradle in IntelliJ and via the CLI, which checkboxes should be used when committing, etc. This popped...
This would probably require a fairly significant rework of the validation functions, but might be nice to implement using a similar technique as this: https://youtu.be/cwJK_WpseKQ?t=5m43s
After doing a single big run (e.g. config_minneapolis_2013_scale.json), the audit log is too big for even Notepad++ to open (700 MB!). We need to figure out a better way to...
Implement the simplest changes specified in the Center for Civic Design Universal Tabulator Redesign Final mockups document (`Tabulator (FINAL mockups) May 2020.docx`). These will mainly consist of moving existing options...
First pass at this can be a simple button that opens up the config_file_documentation.txt. Eventually, it'd be nice to get full on context-sensitive tooltips integrated.
Continuing our discussion in #232: > OK, yeah, I'm pretty confident that IntelliJ is the culprit for all this nonsense. I looked for a bit and couldn't figure out how...