👺 v1.0.0: formatting tweaks + dev env enhancements #7
Conversation
This file contains 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
SimmonsRitchie
changed the title
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.
What's this PR do?
Adds some final polish for v1 release, including:
Why are we doing this?
To ensure the code is clean and the dev environment produces a consistent code style among contributors. The decision to force the spider to close if the sentry DSN wasn't set was to help avoid sneaky errors. Prior to this change, if the dsn wasn't set the extension would simply be disabled and a user might not be aware that the Sentry integration isn't in effect.
Steps to manually test
See #6
Are there any smells or added technical debt to note?
n/a