Repository navigation
feat: suggest umami and mosparo from the packages that use them - #104
Merged
Merged
Conversation
A project that requires still-code/laravel-umami reads its stats from Umami, and one that verifies forms through mosparo/php-api-client needs a mosparo instance. Both now suggest their service, so the setup wizard ticks it and the site's Overview offers it. The mosparo client is matched rather than a framework integration because every integration pulls it in, which puts it in the lock under the Symfony bundle and the TYPO3 extensions alike.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A project that requires still-code/laravel-umami reads its stats from Umami, and one that verifies forms through mosparo/php-api-client needs a mosparo instance. Both now suggest their service, so the setup wizard ticks it and the site's Overview offers it. The mosparo client is matched rather than a framework integration because every integration pulls it in. Lands after lerd-env/services#48 and #49.