Laravel is a web application framework with expressive, elegant syntax. We’ve already laid the foundation for your next big idea — freeing you to create without sweating the small things.
The Laravel documentation.
@bkd27 while working on this I realized we're modifying subscription trials here but what you actually want is to end a customer's generic trial on their user record. Generic trials are a Cashier level thing and cannot be controlled from Stripe. You'll have to implement some custom code using webhooks somehow to get the behaviour that you desire.
As for subscription trials you can already end them whenever you wish when cancelling them from the dashboard:
No, the generic trial is a purely separate thing (That is customer level trial), I am concerned about the subscription trial only, If a subscription is cancelled 'Immediately' in a stripe or via the customer portal, the default behaviour is to if the subscription has a trial on then that should be removed. If that is not then what is the use of cancelling the subscription immediately,
The code that I added controlling that behaviour via config will be handy for that.
Let me know if you have further questions on this.
Any change this package could be updated to use default nextjs 12 packages and options?
Like react 18, removing babel to use swc, and using eslint-config-next instead of various eslint and babel plugins.
Noted ur preference to delay merging this for now. Would you be fine if I make another PR to SimpleMessage class to add the Marcoable trait?
This way I will be able to add methods of my own in run time to the class.
Vite provides a way to specify the name of the
manifest.json, many Laravel projects using a modular structure inside each module have their own
vite.config.js file. Currently, the default file name is
manifest.json I think it will be nice to get the file name from
For the Vite facade need to specify the
manifest.json file name if it's different from
the Laravel mix has a plugin
laravel-mix-merge-manifest to merge bundled files into one
I've created https://github.com/laravel/vite-plugin/pull/150 that will respect the manifest config if provided :+1:
For the Vite facade, you can extend it and override the
This PR addresses https://github.com/laravel/vite-plugin/issues/149 by respecting the users'
build.manifest configuration if provided.
I've conservatively marked this as 0.7 because it could change the behaviour if a user had specified a manifest config, which would previously have been ignored.