Skip to content

Conversation

@thammel
Copy link

@thammel thammel commented Nov 19, 2025

Before:
There was no supported way to rename supplementary files in DictSupplementaryFileContainer. Workflow had to manipulate internals or create duplicates, making file handling error-prone.

Now:
A public rename operation preserves content de-duplication and resolves name conflicts, simplifying AASX read/write flows and reducing inconsistent mappings.

See rwth.aachen/aas-manager#46

Before:
There was no supported way to rename supplementary files in
`DictSupplementaryFileContainer`. Workflow had to manipulate internals or create duplicates, making file handling error-prone.

Now:
A public rename operation preserves content de-duplication and resolves name conflicts, simplifying AASX read/write flows and reducing inconsistent mappings.
@s-heppner
Copy link
Contributor

Thank you, that's a good idea! Could you please also add a unittest for your new method to this TestCase class?

And while you're add it, if you merge develop into your branch (should not have any conflicts, I think), then the check-python-versions CI should pass again.

Merge develop branch

This should resolve CI errors
Merge remote-tracking branch 'upstream/develop' into add/rename-file
@zrgt zrgt merged commit e51e2f8 into eclipse-basyx:develop Dec 10, 2025
15 checks passed
@thammel thammel deleted the add/rename-file branch December 18, 2025 09:14
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.

4 participants