Jess Archer

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Thanks for the PR, and I'm sorry for the delay! I ended up going with a slightly different approach (#592), but this PR was very helpful, and I borrowed your...

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

Hey there, We're closing this issue because it's inactive, already solved, old or not relevant anymore. Feel free to open up a new issue if you're still experiencing this problem.

> In your examples you have routes to destroy a singleton. Shouldn't you also be able to create and store one if it doesn't exist? The intention would be that...

I don't mind adding "resource" to the method name to give more context. I like the definition of ["singleton"](https://www.dictionary.com/browse/singleton) but I'm not married to it either. An alternative could be...

The problem I have with "singular" is that we've already used that word in [`Illuminate\Routing\ResourceRegistrar`](https://github.com/laravel/framework/blob/9.x/src/Illuminate/Routing/ResourceRegistrar.php) (the class where this new functionality lives) for the process of generating the singular version...

I worry the word "creatable" implies that POST requests are the preferred (and perhaps only) way that a singleton resource should be created. Personally, I disagree with the other frameworks...