Brian Faust

@jasonmccreary is the goal here still https://github.com/laravel-shift/blueprint/issues/164#issuecomment-621973749? If so I could work on that next week though it seems like the initial goal in this issue was resolved with https://github.com/laravel-shift/blueprint/pull/530.

Alright, will take a look next week and see which ones are the fastest to test/integrate to see how feasible it is.

Would this syntax be less clutter? We could still derive the `JobCommentController` name and we can treat each segment as a model without the user having to specify the `model`...

@jasonmccreary I experimented with this in https://github.com/faustbrian/blueprint/commit/047c0a8fa6281c9da1888830ead9e823373e757e. The main challenge is statement generation, as most classes rely on the controller name. For nested controllers, we need to adjust the return...

@ryanmitchell, do you think you would have time to rebase this on top of the `4.x` branch? I'm trying to use the `diff` of this PR as a patch via...

@ryanmitchell Thanks, appreciated! Now it works 🎉

@mabadir is there a fixture for this to make sure the request gets parsed correctly?

@jasonmccreary can this be closed based on https://github.com/laravel/framework/issues/1465#issuecomment-18700321?

@holgerd77 it was. Our application keeps crashing at one point because the trie gets corrupted if we use the pruning with tries that use variable-length keys.

@tobyzerner how far out do you think this is? I'm currently evaluating this package for a new project and this would be the main feature missing currently.