Toward a stable API #31
Merged
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
🦋 Changeset detectedLatest commit: 943a258 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Merged
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.
In the process of implementing #22, I ended up making a lot of forward-looking changes to the internal infrastructure and public API.
I’ve been thinking a lot about next steps toward making the UI more useful, allowing you to dig into specific problems and get a lot more details about them. These API changes lay the groundwork for that. (I also have a friend who’s interested in working with me on the UI, which I’m super excited about.) In the meantime, some of the problem summary descriptions may seem to lack important details for package authors trying to determine exactly what’s going on. I think it’s better to get this (huge) PR merged first and iterate on the UI in the coming weeks.
I am a little concerned that in such a big set of changes and with relatively little test coverage that I might have broken something. I may add some more tests before merging.
Closes #22