fix: Fix settings import when a setting is typed#1026
Merged
Conversation
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
If the key is not in the lexicon and was never set it does not have a type yet and that’s fine. Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
Collaborator
Author
|
@DerDreschner thank you for the test, can you try with the new commit? |
DerDreschner
approved these changes
Feb 4, 2026
DerDreschner
left a comment
There was a problem hiding this comment.
@come-nc Yeah, now it works for me. Thanks for the quick fix!
artonge
approved these changes
Feb 4, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

TypeConflictExceptionwhen runningocc user:import#1024