-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Guess, no tags for migrations and config #49
Comments
Thanks for the heads up, I do have some bits to add in when I do the next release. Anything feature-wise that you're wanting? |
Yes, i had 2 moments, that pushed me to fork..
|
Next version addresses a couple of these, Custom db connection for table Some logic to allow checking if something is locked, without locking it. It's a use case I personally don't use (which is why it's not present), but get why it's useful. Plus I will finally get around to properly documenting properly More than happy for PRs btw |
The other key addition in the next release is per-model customisations for over-riding the default behaviours. Apologies that I've not been updating rhe package, there's a chunk of updates in my local environments to bring in |
Sounds great! I'm using it to add a feature i wasn't asked to do. For the moment made quick fixes just in place, - if it be apporved for further development, surely, take part. |
Get
No publishable resources for tag [laravel-lockable-migrations].
No publishable resources for tag [laravel-lockable-config].
The text was updated successfully, but these errors were encountered: