Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

prettier: 3.2.5 -> 3.3.2 #5270

Merged
merged 2 commits into from
Jun 21, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions docs/presets/remote-sources.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -128,9 +128,8 @@ fine.

#### `companionCookiesRule`

This option correlates to the [`Request.credentials` value][], which tells the
plugin whether to send cookies to [Companion](/docs/companion) (`string`,
default: `same-origin`).
This option correlates to the [`Request.credentials` value][], which tells the plugin
whether to send cookies to [Companion](/docs/companion) (`string`, default: `same-origin`).

#### `target`

Expand Down
7 changes: 3 additions & 4 deletions docs/uploader/aws-s3-multipart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -34,10 +34,9 @@ it uploads a single object as a set of parts. This has certain benefits, such as
improved throughput (uploading parts in parallel) and quick recovery from
network issues (only the failed parts need to be retried). The downside is
request overhead, as it needs to do creation, signing (unless you are [signing
on the client][]), and completion requests besides the upload requests. For
example, if you are uploading files that are only a couple kilobytes with a
100ms roundtrip latency, you are spending 400ms on overhead and only a few
milliseconds on uploading.
on the client][]), and completion requests besides the upload requests. For example,
if you are uploading files that are only a couple kilobytes with a 100ms roundtrip
latency, you are spending 400ms on overhead and only a few milliseconds on uploading.

**In short**

Expand Down
4 changes: 2 additions & 2 deletions docs/uploader/tus.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -119,8 +119,8 @@ const headers = {
```

Header values can also be derived from file data by providing a function. The
function receives an [Uppy file][] and must return an object where the keys are
header names, and values are header values.
function receives an [Uppy file][] and must return an object where the keys are header
names, and values are header values.

```js
const headers = (file) => {
Expand Down
4 changes: 2 additions & 2 deletions docs/uploader/xhr.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -130,8 +130,8 @@ const headers = {
```

Header values can also be derived from file data by providing a function. The
function receives an [Uppy file][] and must return an object where the keys are
header names, and values are header values.
function receives an [Uppy file][] and must return an object where the keys are header
names, and values are header values.

```js
const headers = (file) => {
Expand Down
6 changes: 3 additions & 3 deletions yarn.lock
Original file line number Diff line number Diff line change
Expand Up @@ -26299,11 +26299,11 @@ __metadata:
linkType: hard

"prettier@npm:^3.0.3":
version: 3.2.5
resolution: "prettier@npm:3.2.5"
version: 3.3.2
resolution: "prettier@npm:3.3.2"
bin:
prettier: bin/prettier.cjs
checksum: 10/d509f9da0b70e8cacc561a1911c0d99ec75117faed27b95cc8534cb2349667dee6351b0ca83fa9d5703f14127faa52b798de40f5705f02d843da133fc3aa416a
checksum: 10/83214e154afa5aa9b664c2506640212323eb1376b13379b2413dc351b7de0687629dca3f00ff2ec895ebd7e3a2adb7d7e231b6c77606e2358137f2150807405b
languageName: node
linkType: hard

Expand Down