Updated the changelog after recent features/fixes by @haasjona and
@woutervdub
Re-ran reconfigure to update README's with the updated contributor list.
This plugin is used to draft designs for high bust rather than full
chest circumference. To facilitate that, we provide(d) a named export
called `withCondition` that checks whether the plugin is wanted, and if
so loads it.
Problem with that is that the conditional loading of a plugin applied
to the entire pattern. And since we support drafting patterns for
multiple sets (and use this to sample) this means that all of these sets
would either get the plugin effect or not, based on the first set.
So, to fix that, we have changed the lifecycle hook used by this plugin
to `preSetDraft` (from `preDraft`) and changed the `withCondition`
method to always return true.
This means that the plugin will always be loaded, and we have moved the
check that used to be in `withCondition` to the lifecycle hook.
In other words, this plugin will now always be loaded and will check for
each set whether it needs to do something.
This allows the conditionality to apply to each set in the pattern,
rather than to the entire pattern.
Note that conditionally loading plugins pattern-wide is still a valid
use-case. It just so happens that for this plugin, it was the wrong
approach.
- Added:
- core:
- Added the `Path.combine()` method
- The `Path.join()` method is now variadic
- The `Path.length()` now takes an parameter to include move operations in the length calculation
- lumina:
- Initial release
- lumira:
- Initial release
- plugin-annotations:
- The `title` macro now takes a `notes` and `classes.notes` as its config, allowing you to add notes
- The `classes.cutlist` config is removed from the title plugin, cutlist info is now included as notes
- plugin-i18n:
- This plugin now supports translation of nested arrays of strings, giving you more flexibility to concatenate translated parts of strings
- react-components:
- This Pattern component now supports translation of nested arrays of strings, giving you more flexibility to concatenate translated parts of strings
- sandy:
- Added a new *panels* option
- tristan:
- Inital release
- Deprecated:
- core:
- Calling `Path.join` with a second parameter to indicate that the resulting paths most be closed is now deprecated and will be removed in FreeSewing v4.
- Fixed:
- brian:
- Take biceps ease into account when calculating armhole depth
- carlton:
- Fixed a stray seam allowance path on the collar
- charlie:
- The back pocket welt (4) and front pocket facing (8) incorrectly indicated to cut 2 instead of 4 in the cutlist. Fixes#5791
- hugo:
- Fix issue that crashed the design when complete is off. Fixes#6006
- Base pocket opening on pocket height, rather than width of the garment. Fixes#6004
- Removed:
- plugin-annotations:
- The `classes.cutlist` config is removed from the title plugin, cutlist info is now included as notes
Shout-out to @woutervdub and @benjamesben for their many contributotions
to this v3.2 release 🙏
Note that the tests for Lumina are failing, but that's not related to
the chai upgrade, rather it seems these tests fail because of issues in
the design that we'll tackle later (it's a brand new design yet to be
released).
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Added IDs to dimension macros that missed them, causing them to not be shown
- Keep seam allowance out of the binding length calculation
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Corrected part mixup in translation of flag message
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Fixed wrong use of options in a value method. Fixes
- Remove names from old plugins from list option
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- The skirt and curved waistband are now constructed with the ringsector macro
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Replaced all instances of 'seperate' with 'separate' in option names
- Initial release
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Changed defaults to have more rise in the back
- Increase default rise
- Decrease default vertical stretch
- Decreased default back waist dip
- Increased default front waist dip
- Allowed lower values on back exposure, causing back to flare out
- Fix issue with back part when bulge is on and expand is off
- Pocket opening was not drawn on the facing and pocket pieces. Fixes
- Improve placement of the front welt. Fixes
- Rephrased flag message when expand is off to avoid confusion about included seam allowance. Fixes
- Initial release
- Added support for notes in flags
- Removing macros did not always remove the cutlist data in the store. Fixes
- First release of the plugin providing the default packing implementation
- First release of the plugin facilitating drafting a ring sector
- Allow plugins to provide their own packing implementation
- Added named export `cbqc` which exports the constant to approximate a circle with Cubic Bézier curves
- Core will now set `activeMacro` in the store, keeping track of the running macro - Added the `generateMacroIds`, `getMacroIds`, and `removeMacroNodes` store methods
- Fix order in mergeOptions method so user settings take precendence over defaults
- Fix upward snap for snapped percentage option when snap is a simple number
- The conditional loading of plugins had a bug causing them to never be loaded
- Make Path.split() more robust when handling edge-case. Fixes
- Prevent utils.circlesIntersect() from running sqrt on a negative number. Fixes
- Removed unwanted debug output
Recently I refactored the prebuild code. One thing I did not touch (yet)
was the various site dependencies. They were then ported to NX over the
previous system with build priorities we had in place. And while that
was a welcome improvement, it did not really address the bigger picture:
we don't actually need to build any of these dependencies to build the
site.
All we need to do is help NodeJS so it can resolve everything from the
source. So this commit does that by adding a top-level run script
`yarn buildsiteconfigure` which calls `yarn reconfigure` but with the
BUILDSITE variable set.
When that variable is set, the reconfigure script will skip all optional
steps and generate a slightly different package.json file that tells
NodeJS to looks the package from source, rather than to look for the
build files.
After running this script, the prebuild step for the various sites will
run without problems, even on a fresh repo where nothing has ever been
build.
So I've updated the prebuild script in the sites to run this. For local
development, please use `uyarn predev` so that you don't muck with all
the package.json files.
If you do so (by accident or not) a `yarn reconfigure` run will put
everything back in its place.
FreeSewing now uses NodeJS 18 -- specifically lts/hydrogen -- for its
development.
There is no specific reason to run 18, things will still work in 16
(lts/gallium) but Vercel who hosts/builds our sites will be dropping
support for Node 16 in about 6 months, so since we're gearing up for
a new major release (v3) this is the best time for us to also move
to Node 18.
