1
0
Fork 0
Commit graph

23 commits

Author SHA1 Message Date
Benjamin F
ec6edc096b Move cutonfold and grainline macros out of complete blocks 2023-04-27 14:43:18 -07:00
Benjamin F
fe98245ed9 Add cutlists to blocks/slopers 2023-04-26 18:53:16 -07:00
Enoch Riese
0cbc0856f4 fix (cutlist) edits to work with plugin-mirror's new strictness 2023-04-20 10:23:27 -04:00
joostdecock
1d08ff5639 fix(brian): Updated after mirror macro changes 2023-04-15 16:13:41 +02:00
Enoch Riese
0c501f642d update hide config in all designs 2023-03-08 14:37:09 -06:00
Joost De Cock
960cd9ca13 feat(brien): Optimize sleevecap resolver 2022-09-18 18:43:21 +02:00
Joost De Cock
b7d8cef789 fix(brian): Use hide() not setRender() 2022-09-18 18:43:00 +02:00
Joost De Cock
5dc7401308 chore(core): Use hide, not render 2022-09-18 18:16:17 +02:00
Joost De Cock
a416b8b860 chore: More linting 2022-09-15 13:49:55 +02:00
joostdecock
e682966cf2 chore(brian): Port to v3 stage 2 2022-09-10 19:37:33 +02:00
Joost De Cock
d6cc541da3 chore(brian): Adapt to new data file 2022-09-01 08:51:57 +02:00
Joost De Cock
da76819f5a chore(brian): Move plugin config to part-level 2022-08-31 17:53:33 +02:00
Joost De Cock
ca62e4e432 chore: Avoid JSON imports in designs 2022-08-29 17:42:17 +02:00
Joost De Cock
c78962b86a fix(brian): Clean up sleevecap paths/snippets/title from base part 2022-08-29 17:41:58 +02:00
Joost De Cock
bbfef41e98 wip: Post-barcelona wrap-up commit 2022-08-29 08:31:23 +02:00
Joost De Cock
5d899e07c8 chore(brian): Move options into parts 2022-08-28 15:15:44 +02:00
Joost De Cock
e11571f1e1 chore(brian): Switch to new conditional bust plugin export 2022-08-28 14:52:18 +02:00
Joost De Cock
5e31befd0c chore(brian): Use named exports only 2022-08-26 16:34:55 +02:00
Joost De Cock
bee526b341 chore(brian): Ported to v3 2022-08-26 14:45:51 +02:00
joostdecock
70bd946bdc wip(core/brian/aaron): Support for 2022 style part inheritance
This is very rough around the edges, but it's kinda working, so
I'm committing this now.

What this enabled is the ability to extend a part by importing
only that part and then just saying you want a part `from` the
imported one.

The imported part comes with all options, it does not currently
come with all measurements.

This also *follows* dependencies. For example in Brian, we never
explicitly add the base and sleevecap parts, they are simply
added automatically because other parts are buily *from* them.

Best to look at the source code of designs/brian and designs/aaron
to understand what's going on and how it is different.
2022-08-09 20:17:35 +02:00
Joost De Cock
9096353778 feat(brian): Add support for high-bust draft. See #2386 2022-07-09 17:29:20 +02:00
Joost De Cock
46d9f19e7b fix(brian): Make s3 options snap to zero below 10%. Closes #2249 2022-07-09 16:39:21 +02:00
Joost De Cock
e4035b2509 chore: Re-structure workspaces, enforce build order
These are some changes in the way the monorepo is structured,
that are aimed at making it easier to get started.

There are two important changes:

**Multiple workspaces**

We had a yarn workspaces setup at `packages/*`. But our monorepo has
grown to 92 packages which can be overwhelming for people not familiar
with the package names.

To remedy this, I've split it into 4 different workspaces:

- `designs/*`: Holds FreeSewing designs (think patterns)
- `plugins/*`: Holds FreeSewing plugins
- `packages/*`: Holds other packages published on NPM
- `sites/*`: Holds software that is not published as an NPM package,
  such as our various websites and backend API

This should make it easier to find things, and to answer questions like
*where do I find the code for the plugins*.

**Updated reconfigure script to handle build order**

One problem when bootstrapping the repo is inter-dependencies between
packages. For example, building a pattern will only work once
`plugin-bundle` is built. Which will only work once all plugins in the
bundle or built. And that will only work when `core` is built, and so
on.

This can be frustrating for new users as `yarn buildall` will fail.
And it gets overlooked by seasoned devs because they're likely to have
every package built in their repo so this issue doesn't concern them.

To remedy this, we now have a `config/build-order.mjs` file and the
updated `/scripts/reconfigure.mjs` script will enforce the build order
so that things *just work*.
2022-06-16 17:11:31 +02:00