fix: encode metadata keys #2092
Open
+341
−18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can we create 2 utility functions for encode and decode that handles dot ? |
nitrosx
requested changes
Sep 2, 2025
|
We should also add testing for this feature |
…ct/scicat-backend-next into fix-filtersearch-bug
…ct/scicat-backend-next into fix-filtersearch-bug
…ct/scicat-backend-next into fix-filtersearch-bug
…ct/scicat-backend-next into fix-filtersearch-bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In
datasets.service.tsthe metadata keys are now encoded before datasets gets created and updated.Motivation
To ensure correct formatting of metadata key queries for both Elastic Search and MongoDB.
Fixes
Changes:
Tests included
Documentation
official documentation info