Skip to content
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

Update README to Avoid Elixir Warning #762

Merged
merged 1 commit into from
Mar 26, 2024
Merged

Conversation

stratigos
Copy link
Contributor

A warning is issued for use of get_env/2 used outside of a module. The warning suggests using compile_env/3 instead.

This change updates the documentation to conform to this suggestion and remove the warning, resulting in a cleaner and more modern setup for wallaby.

Resolves #761

A warning is issued for use of `get_env/2` used outside of a module.
The warning suggests using `compile_env/3` instead.

This change updates the documentation to conform to this suggestion
and remove the warning, resulting in a cleaner and more modern
setup for `wallaby`.

Resolves [elixir-wallaby#761](elixir-wallaby#761)
@stratigos
Copy link
Contributor Author

This worked just fine in my tests and when running my Phoenix application.

@mhanberg mhanberg merged commit 0c25c04 into elixir-wallaby:main Mar 26, 2024
alinmarsh pushed a commit to TernSystems/wallaby that referenced this pull request Oct 8, 2024
A warning is issued for use of `get_env/2` used outside of a module.
The warning suggests using `compile_env/3` instead.

This change updates the documentation to conform to this suggestion
and remove the warning, resulting in a cleaner and more modern
setup for `wallaby`.

Resolves [elixir-wallaby#761](elixir-wallaby#761)
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.

Suggested Phoenix Configuration for Concurrent Feature Test Issues Warning
2 participants