1
0
Fork 0
Commit graph

13 commits

Author SHA1 Message Date
Enoch Riese
042d4e71a9 [vercel skip] chore (core) document and test Stack.home 2023-04-14 23:49:45 -04:00
Enoch Riese
444d82c527 [vercel skip] fix tests 2023-04-14 16:06:55 -04:00
Enoch Riese
29a0b08a1d use part transforms to calculate stack bounds instead of part bounds 2023-04-14 15:42:22 -04:00
joostdecock
b3679ede55 fix(core): Fixed issue with wrong store for log 2022-09-25 10:55:37 +02:00
joostdecock
12c5c6a3f8 wip(core): Ensure imutable design parts and options 2022-09-25 10:55:37 +02:00
Joost De Cock
bb89b6ca65 chore(core): Unit tests for v3 code 2022-09-19 23:35:52 +02:00
Joost De Cock
200cebf582 chore(core): Refactor v3 code 2022-09-18 15:11:10 +02:00
Joost De Cock
0b18d81e14 feat(core): Added support for multiple sets of settings
This changes they was settings (what the user provides) are handled.
Before this, settings were passed as an object and that was it.
Now, settings are treated as an array of settings objects and this adds
full support for managing multiple sets of settings in a single pattern
instance.

This is the mechanism that's used for FreeSewing's sampling which used
to be a rather hackish implementation, but now merely sets up the
relevant list of settings, and then calls `pattern.draft()` as usual.

Things to be mindful of is that parts, the store and settings themselves
are tied to each set of settings. So where they used to be an object,
they are now an array of object.
2022-09-17 10:24:13 +02:00
Joost De Cock
56427cc4bd chore(core): Linter fixes 2022-09-15 06:34:05 +02:00
Joost De Cock
a953f1692b chore: Prettier run 2022-09-14 15:04:24 +02:00
Joost De Cock
1c442ad580 wip(core): Work on stack-based layouts 2022-09-14 12:24:09 +02:00
Joost De Cock
7ac5a88dff feat(core): Added support for stacks in layout 2022-09-13 17:56:01 +02:00
joostdecock
85748db201 wip(core): Started working on support for stacks in core 2022-09-12 20:10:22 +02:00