Version 12.1.1

Updates

• fix: Change ticket creation endpoint URL from /ticket/ to /tickets/ to follow backend change.

Other updates

• fix(deps): update dependency @types/ws to v8.5.7
• chore(deps): update dependency ts-loader to v9.5.0
• chore(deps): update dependency @types/sinon to v10.0.19
• chore(deps): update dependency typedoc to v0.25.2
• chore(deps): update typescript-eslint monorepo to v6.7.5
• chore(deps): update yarn to v3.6.4
• chore(deps): update dependency eslint-import-resolver-typescript to v3.6.1
• chore(deps): update dependency eslint to v8.51.0
• chore(deps): update dependency @types/node to v18.18.4
• chore(deps): update dependency @babel/core to v7.23.0
• chore(deps): update dependency @types/node to v18.17.18
• fix(deps): update dependency ws to v8.14.2

Full Changelog: v12.1.0...v12.1.1

Version 12.1.0

• lastName is optional in Qminder.Ticket.create
• Fixes issues with fetching temporary API key for GraphQL Subscriptions

Updates

• fix: Fixes to ticket creation update by @boxmein in #639

Other updates

• chore(deps): update typescript-eslint monorepo to v6.7.2 by @renovate in #640
• chore(deps): update dependency @types/node to v18.17.17 by @renovate in #637
• chore(deps): update babel monorepo to v7.22.20 by @renovate in #635
• chore(deps): update dependency @types/jest to v29.5.5 by @renovate in #638
• chore: bump to 12.1.0 by @boxmein in #641

Full Changelog: v12.0.0...v12.1.0

Version 12.0.0

Features

• feat: ticket creation updated by @boxmein in #603

Ticket Creation API update

Input Field IDs

Ticket Creation API, when saving input field data, now references input fields by ID instead of by title. This makes it easier to ensure consistency and confirm that the data arrives at the right input field for your clerks / service personnel.

Input Field Option IDs

Additionally, when using selection input fields, the options also are referenced by ID, which means that colors of options are respected when creating tickets using the API.

Labels in Ticket Create Request

It is also now possible to create a ticket and attach labels in a single request.

Dependency Updates

Dependency updates that affect the runtime:

• fix(deps): update dependency cross-fetch to v4 by @renovate in #624
• fix(deps): update dependency ws to v8.14.1 by @renovate in #626
• chore: bump to 12.0.0 by @boxmein in #634

Full Changelog: v11.2.0...v12.0.0

Version 11.2.0

Version 11.2.0

This version is all about GraphQL real-time subscription quality.

• Reconnecting more + covering with more tests
• If you send an invalid query to the subscription endpoint, you will receive an error back.

What's Changed

• fix: subscription errors propagated to consumers by @boxmein in #582
• fix(ticket): Model improvements by @KarlMae in #599
• chore: bump to 11.2.0 by @boxmein in #600
• fix: when there are open subscriptions, reconnect even on a close code of 1000 by @boxmein in #602

Full Changelog: v11.1.1...v11.2.0

Version 11.1.1

What's Changed

• fix: log when websocket closes by @boxmein in #576
• fix: reconnect to socket for all close codes except 1000 by @boxmein in #577

Full Changelog: v11.1.0...v11.1.1

Version 11.1.0

What's Changed

• feat(webhooks): allow setting custom headers by @stdevi in #565

Full Changelog: v11.0.2...v11.1.0

Version 11.0.2

What's Changed

• chore(deps): update dependency @types/node to v18.16.12 by @renovate in #563
• feat: export TicketStatus by @2ndalpha in #568
• chore(deps): update dependency webpack to v5.83.1 by @renovate in #564
• chore(deps): update dependency @types/node to v18.16.13 by @renovate in #566

Full Changelog: v11.0.1...v11.0.2

Version 11.0.1

Gather additional info during websocket close #559

What's Changed

• chore(deps): update typescript-eslint monorepo to v5.59.6 by @renovate in #557
• chore(deps): update dependency @types/node to v18.16.10 by @renovate in #558
• feat: WebSocket error message logging by @boxmein in #559

Full Changelog: v11.0.0...v11.0.1

Version 11.0.0

Fix for error handling:

Some endpoints were not correctly forwarding errors as the error interface in the API had changed.

Added 3 error types: SimpleError, ComplexError and UnknownError.
Now all the errors from Qminder calls can be checked against one of the provided error types and then be handled accordingly.

Migration guide:

Some endpoints that forwarded the first error from the response error object to the message do not do that anymore. Check for usages of error.message and if they still provide the necessary error message. If the error message has changed, use the proper message from the error object.

Version 10.0.2

Contains a patch for #544