Pydantic state fixes #368
Merged
Pydantic state fixes #368
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
This ensures we don't recompute whatever the data property every time it's called.
elijahbenizzy
force-pushed
the
pydantic-state-fixes
branch
from
8a8698e
to
a089ef7
Compare
skrawcz
reviewed
Sep 18, 2024
| ============ | ||
|
|
||
| .. note:: | ||
| Burr allows you to specify types for your state. This enables more self-documenting, easy-to-write actions, |
There was a problem hiding this comment.
does this build correctly? is whitespace required?
skrawcz
approved these changes
Sep 18, 2024
elijahbenizzy
force-pushed
the
pydantic-state-fixes
branch
from
a089ef7
to
52c1fef
Compare
Adds in some that were left out + rounds out the docs
…e/shifting priorites
elijahbenizzy
force-pushed
the
pydantic-state-fixes
branch
from
52c1fef
to
f5a9b5f
Compare
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.
A few functionality/docs fixes that I missed the first go-around