Skip to content

Conversation

@BasilLangevin
Copy link
Contributor

Currently, the Waterhole::isForumRoute() and Waterhole::isCpRoute() methods only check that the request path matches.

This creates issues when a custom domain is specified in config/system.php, especially when integrated into an existing Laravel project.

This commit adds a check to ensure the domain matches if one is specified in the system config.

Resolves #86

Currently, the `Waterhole::isForumRoute()` and `Waterhole::isCpRoute()` methods only check that the request path matches.

This creates issues when a custom domain is specified in `config/system.php`, especially when integrated into an existing Laravel project.

This commit adds a check to ensure the domain matches if one is specified in the `system` config.
@BasilLangevin
Copy link
Contributor Author

Note: I could not find any testing setup in the repository, so I tested the various configuration permutations in my own application. If you would like me to add tests to this pull request, just let me know where I should put them, and I'll be happy to do so!

Laravel can be configured to use immutable Carbon dates with `Date::use(CarbonImmutable::class)`.

`DateTimeInterface` is the common interface for `DateTime` and `DateTimeImmutable`.

This commit updates `DateTime`-typed parameters to `DateTimeInterface` to support immutable dates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Waterhole::isForumRoute() and Waterhole::isCpRoute() do not validate the request domain

1 participant