Remove some private field modifiers from Router about oak HOT 3 CLOSED

What is the use case of subclassing router, and why does access to private methods make it difficult?

from oak.

@kitsonk So Router has lots of awesome functionality, which I'm sure wasn't trivial to implement. Subclassing the router could have all sorts of use cases, for example in order to programmatically configure the router given a formal API specification. As far as I've been able to tell, it's impossible to call #register or #useVerbs from the outside, so to speak.

Is there any particular reason why these methods are private in the first place?

from oak.

Because they don't make part of the public API of the router.

The oak router is not meant to be derivable. If it is missing features, those would stand on its own merits for consideration. The current abstraction that I want to maintain as part of the project, and would consider exposing non-public methods as not a desire of the project. Therefore, respectfully declined.

from oak.