This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	~7.28.0 -> ~7.29.0

Release Notes

<details> <summary>eslint/eslint</summary>

v7.29.0

Compare Source

• bfbfe5c New: Add only to RuleTester (refs eslint/rfcs#​73) (#​14677) (Brandon Mills)
• c2cd7b4 New: Add ESLint#getRulesMetaForResults() (refs #​13654) (#​14716) (Nicholas C. Zakas)
• eea7e0d Chore: remove duplicate code (#​14719) (Nitin Kumar)
• 6a1c7a0 Fix: allow fallthrough comment inside block (fixes #​14701) (#​14702) (Kevin Gibbons)
• a47e5e3 Docs: Add Mega-Linter to the list of integrations (#​14707) (Nicolas Vuillamy)
• 353ddf9 Chore: enable reportUnusedDisableDirectives in eslint-config-eslint (#​14699) (薛定谔的猫)
• 757c495 Chore: add some rules to eslint-config-eslint (#​14692) (薛定谔的猫)
• c93a222 Docs: fix a broken link (#​14697) (Sam Chen)
• 655c118 Sponsors: Sync README with website (ESLint Jenkins)
• e2bed2e Sponsors: Sync README with website (ESLint Jenkins)
• 8490fb4 Sponsors: Sync README with website (ESLint Jenkins)
• ddbe877 Sponsors: Sync README with website (ESLint Jenkins)

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Code Climate has analyzed commit ae3f0dd5 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 100.0% (0.0% change).

View more on Code Climate.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	~7.28.0 -> ~7.29.0

Release Notes

<details> <summary>eslint/eslint</summary>

v7.29.0

Compare Source

• bfbfe5c New: Add only to RuleTester (refs eslint/rfcs#​73) (#​14677) (Brandon Mills)
• c2cd7b4 New: Add ESLint#getRulesMetaForResults() (refs #​13654) (#​14716) (Nicholas C. Zakas)
• eea7e0d Chore: remove duplicate code (#​14719) (Nitin Kumar)
• 6a1c7a0 Fix: allow fallthrough comment inside block (fixes #​14701) (#​14702) (Kevin Gibbons)
• a47e5e3 Docs: Add Mega-Linter to the list of integrations (#​14707) (Nicolas Vuillamy)
• 353ddf9 Chore: enable reportUnusedDisableDirectives in eslint-config-eslint (#​14699) (薛定谔的猫)
• 757c495 Chore: add some rules to eslint-config-eslint (#​14692) (薛定谔的猫)
• c93a222 Docs: fix a broken link (#​14697) (Sam Chen)
• 655c118 Sponsors: Sync README with website (ESLint Jenkins)
• e2bed2e Sponsors: Sync README with website (ESLint Jenkins)
• 8490fb4 Sponsors: Sync README with website (ESLint Jenkins)
• ddbe877 Sponsors: Sync README with website (ESLint Jenkins)

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

I don't understand this note. I imagine this is about to-one relationships, not to-many. Because for a to-many (as POSTing is adding to, not replacing) there's other relationships which are unknown. So I think the note should be:

Note: This is the appropriate response to a POST request sent to a URL from a to-one relationship link when that relationship already exists. It is also the appropriate response to a DELETE request sent to a URL from a to-one relationship link when that relationship does not exist.

I'm reconsidering this. For to-one relationships it seems one can always return a 204 if it was a success. Whether it changed something or was a race condition doesn't matter.

Otherwise it is still a confusing text for to-many relationships.

(Disclaimer: I'm also an implementer.)

For updating resources I also interpreted the spec as that the response needs to be sent if a for example lastModified field was updated. I didn't think about the scenario where a relationship gets updated due to this. But from a practical point of view I would ignore that. So a PATCH /article/1 would not return any relationships even if they change, and a request to PATCH /article/1?include=author would include the author anyway, no matter if it changes.

For updating relationships I think the spec is a bit incorrect.

Next to:

If a server accepts an update but also changes the targeted relationship(s) in other ways than those specified by the request, it MUST return a 200 OK response. The response document MUST include a representation of the updated relationship(s).

It also states at the 204 No Content response:

Note: This is the appropriate response to a POST request sent to a URL from a to-many relationship link when that relationship already exists. It is also the appropriate response to a DELETE request sent to a URL from a to-many relationship link when that relationship does not exist.

I don't understand this note. I imagine this is about to-one relationships, not to-many. Because for a to-many (as POSTing is adding to, not replacing) there's other relationships which are unknown. So I think the note should be:

Note: This is the appropriate response to a POST request sent to a URL from a to-one relationship link when that relationship already exists. It is also the appropriate response to a DELETE request sent to a URL from a to-one relationship link when that relationship does not exist.

And possible something should be mentioned about to-many as well, like:

Note: This is the appropriate response to a POST request sent to a URL from a to-many relationship link when that relationship is the only relationship (already existing or existing after processing the request). It is also the appropriate response to a DELETE request sent to a URL from a to-many relationship link when that relationship does not exist or was the last relationship.

Or would it be allowed to reply with a 204 on to-many relationship requests in all cases when they are successful? That would for sure safe some server/transfer resources and probably be meaningless to the client anyway. Unless the client wants to update what other clients did in the mean time, but that feels like a minor feature compared to making it required in the spec.

(Btw: does anyone know different words for 'relationship'? Like we name authors on Article a relationship, and we name {'data': [{'type': 'Human', id: '42'}]} a relationship.)

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rollup (source)	~2.51.0 -> ~2.52.0

Release Notes

<details> <summary>rollup/rollup</summary>

v2.52.1

Compare Source

2021-06-17

Bug Fixes

• Fix a memory leak in watch mode (#​4142)

Pull Requests

• #​4142: Make array and object prototype singletons immutable for now (@​lukastaegert)

v2.52.0

Compare Source

2021-06-16

Features

• Add --configPlugin CLI option to apply plugins to the config file for e.g. TypeScript configs (#​3835)
• Add "safest" and "smallest" presets to tree-shaking options for easier configuration (#​4131)
• Add treeshake.correctVarValueBeforeDeclaration option to deoptimize var declarations (#​4139)

Pull Requests

• #​3835: Add typescript config support (@​TheRealSyler)
• #​4131: Add presets to the tree-shaking options (@​lukastaegert)
• #​4139: Add option to deoptimize var declarations for tree-shaking (@​lukastaegert)
• #​4141: Update dependencies (@​lukastaegert)

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Code Climate has analyzed commit f04c4f97 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 100.0% (0.0% change).

View more on Code Climate.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rollup (source)	~2.51.0 -> ~2.52.0

Release Notes

<details> <summary>rollup/rollup</summary>

v2.52.1

Compare Source

2021-06-17

Bug Fixes

• Fix a memory leak in watch mode (#​4142)

Pull Requests

• #​4142: Make array and object prototype singletons immutable for now (@​lukastaegert)

v2.52.0

Compare Source

2021-06-16

Features

• Add --configPlugin CLI option to apply plugins to the config file for e.g. TypeScript configs (#​3835)
• Add "safest" and "smallest" presets to tree-shaking options for easier configuration (#​4131)
• Add treeshake.correctVarValueBeforeDeclaration option to deoptimize var declarations (#​4139)

Pull Requests

• #​3835: Add typescript config support (@​TheRealSyler)
• #​4131: Add presets to the tree-shaking options (@​lukastaegert)
• #​4139: Add option to deoptimize var declarations for tree-shaking (@​lukastaegert)
• #​4141: Update dependencies (@​lukastaegert)

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

We are redesigning one of our APIs that has a lot of requests to check only for true or false, we chose the JSON:API specs for the this api, we couldn't find anything in the specs about (true/false)-only values!

Our API looks like this:

/space/isVacant  ------> response is true or false
/connection/isActive --> response is true or false
/wheather/isRaining ---> response is true or false

The response usually is like this:

{"isVacant": true}
{"isActive": false}
{"isRaining": true}

According to the specs:

A JSON object MUST be at the root of every JSON:API request and response containing data. This object defines a document’s “top level”.

A document MUST contain at least one of the following top-level members:

data: the document’s “primary data” errors: an array of error objects meta: a meta object that contains non-standard meta-information.

And:

Primary data MUST be either:

a single resource object, a single resource identifier object, or null, for requests that target single resources an array of resource objects, an array of resource identifier objects, or an empty array ([]), for requests that target resource collections

And:

“Resource objects” appear in a JSON:API document to represent resources.

A resource object MUST contain at least the following top-level members:

• id
• type

But almost all of the resource don't have id, they are identified by URL only!

What should the response look like? Is any of the following conform to the specs?:

The first:

{
  "meta": {
    "isValid": true // or false
  },
  "data": []
}

The second:

{
  "data": {
    "isValid": true // or false
    // And what about the id and type?
  }
}

The third:

// When true
{
  "data": {
    "isValid": true
    // Again, what about the id and type?
  }
}

// When false
{
  "error": {
    "isValid": false
    // And again, what about the id and type?
  }
}

Any ideas?

Thanks!

Imagine a "parent" and "child" resource, like an order with order lines.

order
  totalPrice: attribute
  orderlines: relationship, to-many orderline

orderline
  order: relationship, to-one order

When you DELETE /orderlines/{id}, the parent order's totalPrice changes. With the current specification, the client must GET /orders/{id} after the DELETE in order to get the updated order data. It would be better if it was possible to include the parent resource after deleting the child resource, e.g. if DELETE /orderlines/{id} could in some way respond with the updated order.

(For the record, #1492 also deals with including resources in responses where currently unsupported, but the issues are distinct.)

should this be moved up one level instead of removed to satisfy the restriction

a resource can not have an attribute and relationship with the same name, nor can it have an attribute or relationship named type or id.

should this be moved up one level instead of removed to satisfy the restriction

a resource can not have an attribute and relationship with the same name, nor can it have an attribute or relationship named type or id.

would this then allow "id" and "type" as attributes member, which violates one of the restrictions for fields?

a resource can not have an attribute and relationship with the same name, nor can it have an attribute or relationship named type or id.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rollup (source)	~2.50.0 -> ~2.51.0

Release Notes

<details> <summary>rollup/rollup</summary>

v2.51.2

Compare Source

2021-06-11

Bug Fixes

• Include modules imported from no-treeshake modules even if they would be empty (#​4138)

Pull Requests

• #​4138: Include all dependencies from modules with no-treeshake (@​lukastaegert)

v2.51.1

Compare Source

2021-06-08

Bug Fixes

• Fix error when using defineConfig (#​4134)

Pull Requests

• #​4134: export rollup.defineConfig at runtime (@​mshrtsr)

v2.51.0

Compare Source

2021-06-06

Features

• Add a helper for IntelliSense support in config files (#​4127)

Bug Fixes

• Improve performance when generating source maps (#​4122)

Pull Requests

• #​4122: User Map to optimize performance (@​izevo)
• #​4127: Export defineConfig defines the auxiliary function of the configuration (@​rxliuli)

v2.50.6

Compare Source

2021-06-03

Bug Fixes

• Do not consider the object spread operator as side effect when propertyReadSideEffects are false (#​4119)
• Detect side effects when returning thenables from async arrow functions (#​4120)

Pull Requests

• #​4119: Respect propertyReadSideEffects in spread elements (@​lukastaegert)
• #​4120: Detect async arrow thenable side effects (@​lukastaegert)

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Code Climate has analyzed commit 00cdb951 and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 100.0% (0.0% change).

View more on Code Climate.

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
rollup (source)	~2.50.0 -> ~2.51.0

Release Notes

<details> <summary>rollup/rollup</summary>

v2.51.2

Compare Source

2021-06-11

Bug Fixes

• Include modules imported from no-treeshake modules even if they would be empty (#​4138)

Pull Requests

• #​4138: Include all dependencies from modules with no-treeshake (@​lukastaegert)

v2.51.1

Compare Source

2021-06-08

Bug Fixes

• Fix error when using defineConfig (#​4134)

Pull Requests

• #​4134: export rollup.defineConfig at runtime (@​mshrtsr)

v2.51.0

Compare Source

2021-06-06

Features

• Add a helper for IntelliSense support in config files (#​4127)

Bug Fixes

• Improve performance when generating source maps (#​4122)

Pull Requests

• #​4122: User Map to optimize performance (@​izevo)
• #​4127: Export defineConfig defines the auxiliary function of the configuration (@​rxliuli)

v2.50.6

Compare Source

2021-06-03

Bug Fixes

• Do not consider the object spread operator as side effect when propertyReadSideEffects are false (#​4119)
• Detect side effects when returning thenables from async arrow functions (#​4120)

Pull Requests

• #​4119: Respect propertyReadSideEffects in spread elements (@​lukastaegert)
• #​4120: Detect async arrow thenable side effects (@​lukastaegert)

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

In a similar situation, this program helped me. The driver distr was removed, and stopped being reinstalled in a circle. https://github.com/lostindark/DriverStoreExplorer/releases/tag/v0.8.3

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
size-limit	~4.11.0 -> ~4.12.0

Release Notes

<details> <summary>ai/size-limit</summary>

v4.12.0

Compare Source

• Added .size-limit.cjs config file support (by Cole Ellison).

</details>

Configuration

📅 Schedule: "before 9am,after 5pm" in timezone Europe/London.

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

• [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

Code Climate has analyzed commit 5f0222cb and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (100% is the threshold).

This pull request will bring the total coverage in the repository to 100.0% (0.0% change).

View more on Code Climate.