Migrate addon to v2 format #391
Closed
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
|
@josephdsumner thank you so much for working on this! I appreciate your help in reviewing #390; since those tests are passing and it resolves additional issues (such as migrating to TS) we'll probably go in that direction, WDYT? |
|
I'm going to close this PR in favor of PR #390 as that's going great! |
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.
This is a copy of an experimental / draft PR that I have been working in my fork of the repository. It intends to migrate the addon to the v2 format and resolve a few related general / housekeeping tasks like updating try scenarios, upgrading ecosystem dependencies, linting fixes, deprecations, etc.
I saw an open PR with similar aims on this repo, so I'm opening mine here for visibility / any collaboration value it might offer.