Remove dependency of requests on Session/Element for layering #67
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.
There's a conceptual layering in the codebase where the Session and Element structs can be built on top of Request structs, but this is not apparent because Request structs refer to Session/Element types. This refactoring is a step towards making this layering explicit. A follow-up will be to pull the requests in separate files.
var
instead oflet
for more swiftiness***Request
variables torequest
since the type is apparent from the contextvar body
properties to computed properties based on fields of the request