kevinschaul / avoid-overlap Goto Github PK

Currently the tests are time-consuming to write, and really I want to test how code changes would affect real-world label scenarios. Can we build a way to export the scenario and parameters out of a project using avoid-overlap and import it into the tests?

• Add all options
• Add example showing arrows as choices
• Add section showing graphics where it's been used

Script the release process? Use GitHub actions? Husky?

Currently the code deletes a label if there is no solution. This should be an option (enable or disable it). Further, there should be a function called when a label is deleted in case the user needs to also take another action like un-highlighting whatever was being labeled.

Currently the implementation does not match the README

We need a debug mode to show where labels started, where they ended up and how they got there.

Possibly this can be implemented as an absolute positioned svg with opacity?