1
0
Fork 0

chore: Remark linter run

This commit is contained in:
Joost De Cock 2022-02-20 14:35:50 +01:00
parent b6dab9f8fa
commit e6f1189017
164 changed files with 395 additions and 395 deletions

View file

@ -3,13 +3,13 @@ title: Adding measurements
order: 130
---
FreeSewing is all about *made-to-measure* sewing patterns;
FreeSewing is all about _made-to-measure_ sewing patterns;
we are going to draft our pattern according to the measurements provided to us.
Which begs the question, which measurements?
It is you, as the pattern designer, who decides which measurements are required to draft your pattern.
For our bib, the only measurement we need is the baby's *head circumference*.
For our bib, the only measurement we need is the baby's _head circumference_.
So let's add it as a required measurement.

View file

@ -3,7 +3,7 @@ title: Adding options
order: 140
---
You know what your bib should look like, and you have the *head* measurement
You know what your bib should look like, and you have the _head_ measurement
to work with. But there's still a number of choices you have to make:
- How large should the neck opening be?

View file

@ -22,8 +22,8 @@ export default function(part) {
}
```
So far, we've kept to the *// Design pattern here* area, but now we're going to work on
the area under *// Complete?*
So far, we've kept to the _// Design pattern here_ area, but now we're going to work on
the area under _// Complete?_
<Note>
@ -122,7 +122,7 @@ However, for future refefence, `sa` is a variable that you can get from `part.sh
just like `complete`. But instead of `true` or `false` it will hold the amount of seam allowance
in mm.
Note that you can still do `if (sa)` because zero is *falsy*.
Note that you can still do `if (sa)` because zero is _falsy_.
We won't be adding seam allowance, but we will be doing something that is essentially the same.
Rather than draw an outline outside our bib to indicate the seam allowance, we'll draw one within
@ -170,10 +170,10 @@ points.scalebox = points.title.shift(-90, 55)
macro("scalebox", { at: points.scalebox })
```
And with that, our pattern is now *complete*:
And with that, our pattern is now _complete_:
<Example pattern="tutorial" part="step11">
We used attributes to add color, dashes, text on a path and even opacity
</Example>
We're not done yet though. There's one more thing the user can ask for: a *paperless* pattern.
We're not done yet though. There's one more thing the user can ask for: a _paperless_ pattern.

View file

@ -62,7 +62,7 @@ points.rightCp1 = points.right
.shift(90, points.bottom.dy(points.right)/2)
```
- We're adding a point named `rightCp1`, which will become the *control point* of the right part
- We're adding a point named `rightCp1`, which will become the _control point_ of the right part
- Instead of using the Point constructor, we're calling the `Point.shift()` method on an existing point
- It takes two arguments: The angle to shift towards, and the distance
- You can see that we're shifting 90 degrees (that means up) but the distance uses another method

View file

@ -124,5 +124,5 @@ it doesn't look much different. We'll use some other classes later that will mak
</Note>
It's looking pretty good. But those sharp corners at the bottom don't exactly say *baby* do they?
It's looking pretty good. But those sharp corners at the bottom don't exactly say _baby_ do they?
Let's fix that.

View file

@ -3,7 +3,7 @@ title: Fitting the neck opening
order: 170
---
Here's how we'll make sure the neck opening is *just right*:
Here's how we'll make sure the neck opening is _just right_:
```js
let tweak = 1
@ -28,7 +28,7 @@ do {
We've added a few new variables:
- `tweak`: A *tweak factor* that we'll use to increase or decrease the neck opening by making it more or less than 1
- `tweak`: A _tweak factor_ that we'll use to increase or decrease the neck opening by making it more or less than 1
- `target`: How long our (quarter) neck opening should be
- `delta`: How far we're off. Positive numbers mean it's too long, negative means too short

View file

@ -25,7 +25,7 @@ let {
} = part.shorthand()
```
The idea behind *paperless patterns* is that users don't need to print your
The idea behind _paperless patterns_ is that users don't need to print your
pattern in order to use it.
Instead, we include dimensions on the pattern that allows them to transfer
the pattern directly onto fabric, or onto an intermediate medium such as tracing paper.
@ -81,7 +81,7 @@ if (paperless) {
}
```
There's a lot going on, but it's mostly repetition. To see what that did to your pattern, you have to enable *paperless mode* in your developing environment; you can find the option under *Pattern options* on the right. Let's look at the end result, and discuss:
There's a lot going on, but it's mostly repetition. To see what that did to your pattern, you have to enable _paperless mode_ in your developing environment; you can find the option under _Pattern options_ on the right. Let's look at the end result, and discuss:
<Example pattern="tutorial" part="bib" settings_paperless="true">
Your paperless bib

View file

@ -45,7 +45,7 @@ This is the boilerplate of our `draftBib` method. It takes the part as an argume
<Note>
If you're new to JavaScript, and don't intuitively *get this*, stick with it. It will become second nature soon enough.
If you're new to JavaScript, and don't intuitively _get this_, stick with it. It will become second nature soon enough.
</Note>
@ -61,7 +61,7 @@ let {
```
This is FreeSewing's **shorthand** method. It returns an object with a bunch of handy helpers
and you use JavaScript's *object destructuring* to only get what you need.
and you use JavaScript's _object destructuring_ to only get what you need.
The example above makes the following variables available:
@ -75,9 +75,9 @@ These will make it possible for you to draw points and paths easily.
The following three variables are also needed to create a full-fledged FreeSewing pattern; their function and usage will
be covered in detail [later on in this tutorial](/tutorials/pattern-design/completing-your-pattern/):
- `complete`: create a *complete* pattern (or not)
- `sa`: include *seam allowance* (or not)
- `paperless`: allow the pattern to be *paperless*
- `complete`: create a _complete_ pattern (or not)
- `sa`: include _seam allowance_ (or not)
- `paperless`: allow the pattern to be _paperless_
For now, we only need these so that the pattern skeleton compiles properly.

View file

@ -11,7 +11,7 @@ and the range of options we provided.
###### No more grading
FreeSewing patterns are *made-to-measure*, which means that you don't need to
FreeSewing patterns are _made-to-measure_, which means that you don't need to
grade your pattern to provide a range of sizes. You should sample your pattern
for different measurements and options to see how well it adapts.
@ -87,13 +87,13 @@ If we test it, we can see that it works as intended. But there's one thing that
Making the bib wider shortens the length from the bottom of the neck opening to the bottom of the bib.
Thereby making the bib shorter when it's worn.
Even if the *total length* of the bib stays the same, the *useable length* shortens when the bib is made wider.
Even if the _total length_ of the bib stays the same, the _useable length_ shortens when the bib is made wider.
Users will not expect this, so it's something that we should fix in our pattern.
<Note>
Adjusting the pattern to make the `widthRatio` not influence the *useable length* of the bib is not
covered in this tutorial. It is left *as an exercise to the reader*.
Adjusting the pattern to make the `widthRatio` not influence the _useable length_ of the bib is not
covered in this tutorial. It is left _as an exercise to the reader_.
</Note>
@ -137,7 +137,7 @@ Your bib with the head circumference measurement sampled </Example>
## Testing models
Whereas testing a measurement will only vary one individual measurement, testing models will
draft your pattern for different sets of measurments, which we refer to as *models*.
draft your pattern for different sets of measurments, which we refer to as _models_.
On the surface, the result below is the same as our measurement test. But that is because our bib
only uses one measurement. So testing that one measurement ends up being the same as testing a complete
@ -173,16 +173,16 @@ Your bib sampled for a range of baby sizes </Example>
## The antperson test
A special case of model testing is the so-called *antperson test*.
It drafts your pattern with a set of *typical* measurements , and then drafts it again
with measurements that are 1/10th of those *typical* measurements.
A special case of model testing is the so-called _antperson test_.
It drafts your pattern with a set of _typical_ measurements , and then drafts it again
with measurements that are 1/10th of those _typical_ measurements.
It is named after [the cartoon character](https://en.wikipedia.org/wiki/Ant-Man_\(film\)) who can shrink,
yet somehow his suit still fits.
The purpose of the antperson test is to bring out areas in your pattern where you made assumptions
that will not properly scale.
Many drafting books will tell you to *add 3cm there* or *measure 2 inch to the right*. Those instructions
Many drafting books will tell you to _add 3cm there_ or _measure 2 inch to the right_. Those instructions
don't scale, and you should avoid them.
The best patterns will pass the antperson test with 2 patterns exactly the same, where one will simply be 1/10th the scale of the other.

View file

@ -3,7 +3,7 @@ title: Your first part
order: 120
---
Much like garments themselves, patterns are made up of *parts*.
Much like garments themselves, patterns are made up of _parts_.
Most patterns will have multiple parts. A sleeve, a back part, the collar, and so on.
Our pattern is very simple, and only has one part: the bib.
@ -14,7 +14,7 @@ button in your browser, you'll get to see it:
![The default pattern with its box part](./step1.png)
Since we only need one part, we'll rename this *box* part, and call it *bib*.
Since we only need one part, we'll rename this _box_ part, and call it _bib_.
## Rename the box part to bib
@ -59,7 +59,7 @@ Pattern.prototype.draftBib = draftBib
###### Always use draftPartname
FreeSewing will expect for each part to find a method named Draft*Partname*.
FreeSewing will expect for each part to find a method named Draft\_Partname\_.
If you have a part named `sleeve` you should have a method called `draftSleeve()` that drafts that part.