-
-
Notifications
You must be signed in to change notification settings - Fork 21
Fixes for installations/content types without i18n #302
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
Conversation
🦋 Changeset detectedLatest commit: 6f1ca00 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #302 +/- ##
==========================================
- Coverage 40.87% 40.48% -0.40%
==========================================
Files 2 2
Lines 614 615 +1
Branches 146 149 +3
==========================================
- Hits 251 249 -2
- Misses 290 295 +5
+ Partials 73 71 -2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I've added some more commits for small fixes and to get the playground working on Windows. |
Yalc uses the `LOCALAPPDATA` environment variable to determine where to put local packages. Without this change, turbo does not propagate `LOCALAPPDATA` to the `build` commands in packages. The packages get published to ``%HOME%\.yalc` instead of `%LOCALAPPDATA%\Yalc`. This means that `playground:publish` will not find them in `%LOCALAPPDATA%\Yalc`.
boazpoolman
left a comment
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.
Tested and approved!
What does it do?
My PR #291 causes a bug when updating / bulk generating documents that have no locale.
Why is it needed?
When updating a documents alias without a locale, a
-0is always appended.How to test it?
Create a content type without internationalization and create a document with that type. Then update it.