Add support for supplied transmission attachment ID on create/update #1241
Assignees
Comments
4 tasks
oskogstad
added a commit
that referenced
this issue
Oct 7, 2024
…pdate (#1242) <!--- Provide a general summary of your changes in the Title above --> ## Description <!--- Describe your changes in detail --> ## Related Issue(s) - #1241 ## Verification - [ ] **Your** code builds clean without any errors or warnings - [ ] Manual testing done (required) - [ ] Relevant automated test added (if you find this hard, leave it and we'll help out) ## Documentation - [ ] Documentation is updated (either in `docs`-directory, Altinnpedia or a separate linked PR in [altinn-studio-docs.](https://github.com/Altinn/altinn-studio-docs), if applicable) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced `id` properties in `CreateDialogTransmissionAttachmentDto` and `UpdateDialogTransmissionAttachmentDto` for better management of transmission attachments. - Added validation rules for `Id` properties to ensure they are valid UUID version 7 with past timestamps. - **Bug Fixes** - Enhanced validation logic during dialog creation and updates to prevent duplicate transmission attachments. - **Documentation** - Updated XML comments for clarity and consistency. These changes enhance the API's functionality, ensuring better tracking and validation of transmission attachments. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: