Skip to content
This repository was archived by the owner on Jun 5, 2025. It is now read-only.

Conversation

@JAORMX
Copy link
Contributor

@JAORMX JAORMX commented Jan 23, 2025

Ultimately all operations will work regardless of the case. Though the
final storage format will be lowercase.

This also made changes to the db models to disambiguate the names from one another.

Closes: #726

@JAORMX JAORMX force-pushed the case-insensitivity branch from c4ba063 to fa31923 Compare January 23, 2025 08:23
Ultimately all operations will work regardless of the case. Though the
final storage format will be lowercase.

Signed-off-by: Juan Antonio Osorio <[email protected]>
@JAORMX JAORMX force-pushed the case-insensitivity branch from fa31923 to 1e452bc Compare January 23, 2025 08:28
aponcedeleonch
aponcedeleonch previously approved these changes Jan 23, 2025
Signed-off-by: Juan Antonio Osorio <[email protected]>
@JAORMX JAORMX merged commit 184ad5e into main Jan 23, 2025
4 checks passed
@JAORMX JAORMX deleted the case-insensitivity branch January 23, 2025 08:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workspace name case sensitivity inconsistent

3 participants