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

Addressing State being consistent in value from the first check (#90) #91

Merged
merged 2 commits into from
Jan 26, 2024

Conversation

0xLeif
Copy link
Owner

@0xLeif 0xLeif commented Jan 26, 2024

  • Update README.md
  • change variable appState name to usernameState to reflect the value of the variable.
  • Update README.md
  • update appState variable name to usernameState for the whole read and write section
  • Made changes to State to cache value when it is first retrieved. Added a test to ensure that state value is consistent from when it is first checked

  • Made additions to testStateClosureCachesValueOnGet to account for async

* Update README.md

- change variable appState name to usernameState to reflect the value of the variable.

* Update README.md

- update appState variable name to usernameState for the whole read and write section

* Made changes to State to cache value when it is first retrieved.
Added a test to ensure that state value is consistent from when it is first checked

* Made additions to testStateClosureCachesValueOnGet to account for async
@0xLeif 0xLeif added the bug Something isn't working label Jan 26, 2024
@0xLeif 0xLeif merged commit 5ce030f into main Jan 26, 2024
3 checks passed
@0xLeif 0xLeif deleted the bug/initial-state branch January 26, 2024 21:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants