Skip to content

Conversation

@susnux
Copy link
Contributor

@susnux susnux commented Mar 18, 2025

Summary

This adds a non-initial-state capability for the
windows-compatibile-filenames feature.
It is not required by the webui and it might have performance impacts (always compares system config against windows presets), so it is not included in every page load, but instead for querying from the clients.

Checklist

@susnux susnux added this to the Nextcloud 32 milestone Mar 18, 2025
@susnux susnux requested a review from a team as a code owner March 18, 2025 15:26
@susnux susnux requested review from Altahrim, come-nc and provokateurin and removed request for a team March 18, 2025 15:26
Copy link
Member

@provokateurin provokateurin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but OpenAPI needs to be updated

@susnux susnux force-pushed the feat/add-wcf-cap branch from 9a8de0b to cbac3b8 Compare March 18, 2025 15:33
@susnux
Copy link
Contributor Author

susnux commented Mar 18, 2025

LGTM, but OpenAPI needs to be updated

✅ done

This adds a non-initial-state capability for the
windows-compatibile-filemnames feature.
It is not required by the webui and it might have performance impacts
(always compares system config against windows presets), so it is not
included in every page load, but instead for querying from the clients.

Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
@susnux susnux force-pushed the feat/add-wcf-cap branch from cbac3b8 to a697da3 Compare March 18, 2025 16:02
@susnux susnux requested a review from come-nc March 18, 2025 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Expose a Boolean Flag for Enforce Windows Compatibility

5 participants