Bump mittwald/api-client from 2.1.44 to 2.1.50

[dependabot]

Bumps mittwald/api-client from 2.1.44 to 2.1.50.

Release notes

Sourced from mittwald/api-client's releases.

v2.1.50

New Features

Added MiscClient, NexusClient, and TaskClient

Three new clients have been introduced to the API client:

• MiscClient: This client is designed for handling API endpoints that are not related to any specific domain.
• NexusClient: This client allows management of Nexus workspaces.
• TaskClient: This client facilitates management of tasks for users and departments.

Enhanced Conversation Schema

The Conversation schema has been expanded to include:

• lastMessage: A new property capturing details about the last message sent in a conversation, enhancing the context available for each conversation.

Changes

• The Client interface now includes methods for task(), nexus(), and misc().
• Implementation classes for the newly added clients (MiscClient, NexusClient, TaskClient) have been created.
• The format of the Conversation schema has been updated with new methods to handle lastMessage, including:
  • getLastMessage()
  • withLastMessage(ConversationLastMessage $lastMessage)
  • withoutLastMessage()
• A new class ConversationLastMessage has been added to encapsulate details of the last message sent within a conversation.

Removed Entities

• Unused department cases have been pruned from the Department enum for better clarity and conciseness.

v2.1.49

Features

• Enhanced Customer Management: Added a new mechanism to handle bad requests in the customer listing functionality, improving error handling.
• Multi-Factor Authentication (MFA) Support: Integrated MFA attributes into the user schemas, including fields for active and setup states, to enhance user security management.
• Password Update Tracking: Introduced a new field to track when the user's password was last updated.

Improvements

• ListCustomersRequest Enhancements: Added a search parameter to ListCustomersRequest, allowing for filtered customer searches. The input validation has also been refined to ensure robust data handling.
• Structured Error Responses: The ListCustomersBadRequestResponse class has been implemented to provide clearer error messages when bad requests occur, streamlining client-side error management.
• Unified MFA Handling: Introduced UserMfa and UserInternalMfa classes to encapsulate MFA-related data accurately, ensuring consistent management across different user contexts.

Bug Fixes

• Improved error handling in CustomerClientImpl by implementing a case for 400 response codes to ensure that users receive appropriate feedback during bad requests.

v2.1.48

Features

• Enhanced Pagination and Limit Control: Introduced limit, skip, and page properties to the NotificationsListNotificationsRequest class to provide better control over the number of notifications returned and pagination support.

New Properties

... (truncated)

Commits

• b8372e7 feat: add new clients and last message support to conversation schema
• 09ba95e feat: add search parameter to ListCustomersRequest and extend User schema wit...
• 6c2ed71 feat: add pagination parameters to NotificationsListNotificationsRequest
• 0d9476e refactor: simplify user ID handling and remove unnecessary alternatives
• cf92026 feat: add frontendFragments property and methods to Extension schema
• 762d200 feat: add pagination parameters to ListProjectsRequest and ListServersRequest
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #172.