-
Notifications
You must be signed in to change notification settings - Fork 56
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
Rewrite domain restrictions #14
base: master
Are you sure you want to change the base?
Conversation
This will allow for a more configurable system where you can specify a full domain name, all subdomains, a tld and port numbers.
This looks awesome, I'm going to have a proper look in the morning. Thanks so much for this @krve! |
Would be nice if we could add some tests into the domain restrictions to ensure it's working correctly |
I'll see if I can't create some tests for the domain restrictions this weekend. |
I also extracted the domain restricter to a specific class to keep it self-contained and make it easier for testing purposes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work @krve, looks much better 👍
But not really backwards compatible for people using current version? |
Sorry, been hectic at work today! Will definitely review this early next week. |
Completely forgot about that @Jaspur. Will look into it this weekend to make sure it has some backwards capability. |
If you think backwards compatibility is going to be an issue, I would be happy to consider making this a breaking change and publishing a new version of the package. |
Yeah, I think that's a better idea. This way we don't have code specifically for an old version of the package. |
Cool. I'm thinking about merging all these recent PRs and just releasing a new |
@mrterryh yeah, that seems like a good idea. |
Just to let you know, I've still got this on my to-do list! Super hectic at work. I'll look ASAP, I promise! |
I tried your package as I need custom domains but I get the following error:
|
@DODMax on what version of Laravel? |
@DODMax I'll take a look at it today when I'm home and fix the issue. |
Moved the initialization to the boot method and make use of laravels Dependency Injection.
@DODMax Just pushed an update that should fix the issue 👍 |
@krve Works like a charm. Thanks for the PR! |
@mrterryh - You wanna merge this? I kinda want to get this one merged so I can work on some of the other issues. |
I'm very surprised nothing ever happened with this. I just hacked it a bit to work with an existing application that is still basically Laravel 5.2. And while it had some issues.. I was able to get it to do what I wanted. |
This error has been a pain, and i see this PR addresses it well, any ETA on when this is going to be released. I prefer not to use a fork as it will be a pending task to switch back to original repository, else would miss all the other enhancements. |
I've made a draft of how the domain validation could work according to #1