-
Notifications
You must be signed in to change notification settings - Fork 1
feat(scenarios): add scenario builder to sdk #706
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
Conversation
4ffbf98 to
980a9ff
Compare
341c74d to
f1b1ca6
Compare
james-rl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some feedback for helpful docstring messages.
…rage matches sync
…ces to RunloopSDK() to 'runloop' instead of 'sdk' or 'client'
177dbda to
034399b
Compare
james-rl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks very close to being ready. The only change I think you need to make is to have the builder use a build() method and then to call push() on the constructed object.
Just to be clear, this is not a matter of correctness, it's about adhering to conventions and user expectations.
| "validation_type": self._validation_type, | ||
| } | ||
|
|
||
| def preview(self) -> ScenarioPreview: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like this approach
james-rl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, nice work!
No description provided.