Create a monorepo to separate v1 addon from test-app #916
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
BlueCutOfficial
force-pushed
the
step3-v1-with-monorepo
branch
4 times, most recently
from
7af3eba to
62aec6f
Compare
BlueCutOfficial
force-pushed
the
step3-v1-with-monorepo
branch
from
62aec6f to
b188865
Compare
BlueCutOfficial
force-pushed
the
step3-v1-with-monorepo
branch
from
b188865 to
d57ec04
Compare
BobrImperator
approved these changes
Feb 7, 2024
BlueCutOfficial
force-pushed
the
step3-v1-with-monorepo
branch
from
e214444 to
d62ea56
Compare
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.
This PR is a step of the conversion to v2 addon. It restructures the v1 addon into a monorepo to separate the addon itself from the dummy app (now called test-app).
At this point, the addon and the test-app are intended to work exactly as before: the linter and test scenarios pass, and a new version of the v1 addon could be released (though we didn't plan to do a release at this stage).