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.
I think that the repo does have a nice configuration factor in the proposed
.env.example
.But I think that the Google Analytics ID also should be among them inside the .env
Maybe not because it has to do with the specific environment you are in but as I said i would like to have it there for the configuration factor. Or would you prefer to add it to the
config\app.php
file?Anyhow, I think it would feel right to add the GA ID to a config level.
I tried to follow what seems to be your convention in the .env and not write out default values inside the .env but where the value is called from. So in the
ga.blade.php
there is this line:{{ env( 'GOOGLE_ANALYTICS_ID', 'UA-XXXXX-X' )}}
What do you think?