@escape.tech/[email protected]

Minor Changes

• 3b204b6: refactor(apollo): throwOnRejection #220

  • throwOnRejection became propagateOnRejection.

  • Apollo will now report to context by default.
    Errors might be very verbose but this is the best way to handle it until Apollo Server 4 is released.
    If you want to still throw errors, you can use the onReject callback, however, you will need to handle the HTTP 500 afterwards yourself.

@escape.tech/[email protected]

Minor Changes

• 3b204b6: refactor(apollo): throwOnRejection #220

  • throwOnRejection became propagateOnRejection.

  • Apollo will now report to context by default.
    Errors might be very verbose but this is the best way to handle it until Apollo Server 4 is released.
    If you want to still throw errors, you can use the onReject callback, however, you will need to handle the HTTP 500 afterwards yourself.

@escape.tech/[email protected]

Minor Changes

• 3b204b6: refactor(apollo): throwOnRejection #220

  • throwOnRejection became propagateOnRejection.

  • Apollo will now report to context by default.
    Errors might be very verbose but this is the best way to handle it until Apollo Server 4 is released.
    If you want to still throw errors, you can use the onReject callback, however, you will need to handle the HTTP 500 afterwards yourself.

@escape.tech/[email protected]

Minor Changes

• 3b204b6: refactor(apollo): throwOnRejection #220

  • throwOnRejection became propagateOnRejection.

  • Apollo will now report to context by default.
    Errors might be very verbose but this is the best way to handle it until Apollo Server 4 is released.
    If you want to still throw errors, you can use the onReject callback, however, you will need to handle the HTTP 500 afterwards yourself.

@escape.tech/[email protected]

Minor Changes

• 3b204b6: refactor(apollo): throwOnRejection #220

  • throwOnRejection became propagateOnRejection.

  • Apollo will now report to context by default.
    Errors might be very verbose but this is the best way to handle it until Apollo Server 4 is released.
    If you want to still throw errors, you can use the onReject callback, however, you will need to handle the HTTP 500 afterwards yourself.

@escape.tech/[email protected]

Minor Changes

• 3b204b6: refactor(apollo): throwOnRejection #220

  • throwOnRejection became propagateOnRejection.

  • Apollo will now report to context by default.
    Errors might be very verbose but this is the best way to handle it until Apollo Server 4 is released.
    If you want to still throw errors, you can use the onReject callback, however, you will need to handle the HTTP 500 afterwards yourself.

@escape.tech/[email protected]

Patch Changes

• 542b49d: fix:
  Incorrect @escape.tech/graphql-armor-types dependency
• Updated dependencies [542b49d]
  • @escape.tech/[email protected]

@escape.tech/[email protected]

Patch Changes

• 542b49d: fix:
  Incorrect @escape.tech/graphql-armor-types dependency

@escape.tech/[email protected]

Patch Changes

• 542b49d: fix:
  Incorrect @escape.tech/graphql-armor-types dependency

@escape.tech/[email protected]

Minor Changes

• c16a2bb: v1.3.0

  • Feat(plugins)/provide-custom-configuration-callbacks #162
  • Refactor(apollo): changed protection default behavior to contextual report #191
  • Chore(deps): new types packages (@escape.tech/graphql-armor-types)
  • Chore(deps): updated devDependencies

Patch Changes

• Updated dependencies [c16a2bb]
  • @escape.tech/[email protected]
  • @escape.tech/[email protected]
  • @escape.tech/[email protected]
  • @escape.tech/[email protected]
  • @escape.tech/[email protected]