The system for creating Convention-based names in Restier is not predictable, testable, or usable by external libraries.

Breakdance was originally called Testier, and it was designed to use Reflection to test an EntityFrameworkApi to see if it could find the method names that Restier was expecting. The result of that process was a well-documented and itself heavily-tested Factory for generating method names based an abstracted Restier pipeline.

You can see this in action here: ConventionBasedMethodNameFactory

Importing this into Restier and making it public would allow other tools to predictably rely on Restier's naming conventions to enhance the ecosystem in other ways.