chore: Merged in left behind PRs from markdown repo
This commit is contained in:
parent
b34a2ee2ed
commit
97b8a93a85
126 changed files with 2327 additions and 486 deletions
|
@ -4,7 +4,7 @@ for: developers
|
|||
about: Shows you how to create dependencies between pattern parts
|
||||
---
|
||||
|
||||
Part dependencies are set in the [pattern configuration](/config), and
|
||||
Part dependencies are set in the [pattern configuration](/reference/config), and
|
||||
control the order in which parts are drawn. FreeSewing will make sure
|
||||
that before drafting a part, it will first draft all its dependencies.
|
||||
|
||||
|
@ -21,7 +21,7 @@ dependencies: {
|
|||
This could be from a T-shirt pattern where the `front` and `back` patterns are very similar,
|
||||
so they both are inheriting a `base` part.
|
||||
In addition, the `sleeve` part needs to be drafted after the `front` and `back` part because
|
||||
in `front` and `back` we store the length of the armhole seam in the [store](/api/store) and
|
||||
in `front` and `back` we store the length of the armhole seam in the [store](/reference/api/store) and
|
||||
we need that info to fit the sleevecap to the armhole.
|
||||
|
||||
Now if a user requests to draft only the `sleeve` part, FreeSewing will still draft:
|
||||
|
@ -34,6 +34,6 @@ but it will only render the `sleeve` part, as that's the only thing the user req
|
|||
|
||||
<Note>
|
||||
|
||||
For inheriting parts, please refer to [part inheritance](/howtos/core/inject/).
|
||||
For inheriting parts, please refer to [part inheritance](/howtos/code/inject/).
|
||||
|
||||
</Note>
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue