Minimise quit state checking in help example #1252
Open
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
Currently, everytime the view is rendered, the app checks for the
quitting boolean which seems unnecessary. This approach simply returns
a unique view for quitting which removes the need for a `quitting` boolean
variable an the `if quitting {...}` check currently run on every
`View()`.
ChausseBenjamin
requested review from
meowgorithm and
aymanbagabas
as code owners
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.
Currently, every time the view is rendered, the app checks for the
quitting boolean which seems unnecessary. This approach simply returns
a unique view for quitting which removes the need for a
quittingbooleanvariable an the
if quitting {...}check currently run everytimemodel.View()gets called.