Replies: 1 comment
-
|
@GeoSot, sorry for the delayed response, & thanks for some good suggestions makes sense. Most of them overlap with what we are planning for our future release plan which is currently in the planning stage Laravel Decomposer |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi . You have done a great Job
If you would like to add some more interesting features on your project, i guess some caching on the values and a config file would be great
Some of the values cost too much time and resources so they could be cached for sometime or by session (maybe a choice config file)
And in a config file you could add the route and some middleware that anyone wish to add, plus the pagination number
Finally you can give the choice to full integrate the decomposer view, in every project. The view could be published in order to by able to modify.
And an adition of the last minute
On some servers, for security reasons some function are disabled. (ex:php_uname)
As a result the code brakes an gets errors
It could be checked with ini_get('disable_functions') before use
Beta Was this translation helpful? Give feedback.
All reactions