Skip to content

feat: integrate beta branch changes including sound events, model fixes and CI improvements#103

Open
theEvilReaper wants to merge 90 commits intonextfrom
beta
Open

feat: integrate beta branch changes including sound events, model fixes and CI improvements#103
theEvilReaper wants to merge 90 commits intonextfrom
beta

Conversation

@theEvilReaper
Copy link
Contributor

Proposed changes

The pull request adds the latest changes from the beta to the next branch including important fixes for the model handling in several cases.

Types of changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

  • I have read the CONTRIBUTING.md
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

theEvilReaper and others added 30 commits March 10, 2026 10:32
… generation (#20)

* fix(attribute): Use operationId to improve attribute client generation

* fix(font): Use operationId to improve font client generation

* fix(item): Use operationId to improve item client generation

* fix(notification): Use operationId to improve notification client generation

* fix(sound): Use operationId to improve sound client generation

---------

Co-authored-by: theEvilReaper <theEvilReaper@users.noreply.github.com>
* fix(dependencies): update vulpes.model version to 1.6.0-beta.5

* feat(tests): add Faker library for enhanced JUnit test data generation

* feat(sound): add toEntity method in SoundFileSourceDTO for entity conversion

* feat(sound): enhance SoundService with methods for managing linked sound file sources

* feat(sound): add methods for creating, updating, and deleting linked sound sources

* feat(sound): add endpoints for managing linked SoundFileSources in SoundController

* feat(tests): add application-test.yml for test environment configuration

* feat(tests): add unit tests for SoundController methods

* feat(tests): add integration tests for SoundController endpoints

* feat(build): update author information and add publish URL in build.gradle.kts

* feat(sound): enhance API documentation for getSoundSourcesById endpoint

* feat(sound): rename schema name in SoundResponseDTO for clarity

* feat(notification): update schema name for clarity in NotificationModelErrorDTO

* feat(item): update schema name for clarity in ItemModelErrorDTO

* feat(sound): add error handling and documentation for add sound event endpoint

* feat(sound): update test to use sampleEventDTOWithoutId for sound event creation

* feat(tests): Rename test class

* feat(tests): Improve import handling

* feat(test): integrate Testcontainers for SoundController tests and update configuration

* feat(gitignore): add test-resources-port.txt to Docker ignore list

* feat(tests): remove unused import from SoundControllerIntegrationTest

* feat(ci): add QEMU and Docker Buildx setup to build pipeline

* feat(ci): update Docker setup action in build pipeline

* feat(ci): remove QEMU setup from build pipeline

* feat(tests): replace Testcontainers with EnabledIfDockerAvailable in SoundControllerIntegrationTest

* feat(ci): remove Docker setup from build pipeline

---------

Co-authored-by: theEvilReaper <theEvilReaper@users.noreply.github.com>
* fix(SoundController): remove unnecessary @Valid annotation from get method

* fix(SoundController): remove unnecessary @Valid annotation from source methods
TheMeinerLP and others added 30 commits March 10, 2026 10:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants