You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 1, 2023. It is now read-only.
Just throwing out an idea that it could be useful to see slight permutations of the same machine adding additional functionality. A simple example would be to permute the “ Simple Data Fetch” machine to use the AbortController to actual cancel the request.
This would allow use to start with trivial examples and build up more complex, intricate examples while allowing someone new to start from an easy to understand example.
I think there are some examples in the catalogue where we are implicitly doing this, but i suspect modifying the current design could help make it more explicit that a group of example build on each other.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just throwing out an idea that it could be useful to see slight permutations of the same machine adding additional functionality. A simple example would be to permute the “ Simple Data Fetch” machine to use the
AbortController
to actual cancel the request.This would allow use to start with trivial examples and build up more complex, intricate examples while allowing someone new to start from an easy to understand example.
I think there are some examples in the catalogue where we are implicitly doing this, but i suspect modifying the current design could help make it more explicit that a group of example build on each other.
The text was updated successfully, but these errors were encountered: