[WIP] feat: alloy migration #50
Draft
Conversation
This file contains hidden or 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
|
picking this back up in the weekend, mostly only it tests to fix. |
|
Hello, has the Alloy migration been abandoned? I'd be willing to implement or contribute to it. |
|
No sorry, just been busy. Only tests are left—will take care of it soon! |
|
Nice, lmk if you're open to my contribution on the test suite ? |
Merged
|
Very anticipated feature, happy to contribute if needed :) |
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.
WIP. Migrates the entire repo to use exclusively alloy types. Closes #49.
considering that now all the types are in alloy, do we want to re-export them here to enable the prev experience?