-
Notifications
You must be signed in to change notification settings - Fork 226
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
Overhaul swingset configuration #1381
Conversation
It looks like some more changes landed on trunk after you branched off (but not mine, so I think they won't conflict). I'm going to experiment with github's "Update branch" button and see what it does. I think we'll want to rebase this whole thing before landing, to avoid the little rats nest of branches that this button will probably create. |
Yep, that button created a merge commit between the branch you pushed and current trunk, which is more messy than we'd want to land. But a |
4cd6ad7
to
06151c6
Compare
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 pretty good. I"m still nervous about YAGNI, but I like everything here. A few minor changes to make, feel free to land once those are done.
06151c6
to
6a4dee8
Compare
Modulo one issue that seems related to loopback (#1381), all tests pass, but there's a little more work to do. A few pieces of Zoe don't use Far classes. This should be a simple update.
These changes implement the new swingset configuration model per #1331. A writeup of the deltas is in the file
APIChange.md
(which should probably be rehomed or renamed or incorporated into some other file, but I wanted to get these changes documented without delaying for the time it would take me to get clear on the change notes publication flow).