Skip to content

Allow workspace operations to work without caring about the case #736

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 23, 2025

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 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.

Workspace name case sensitivity inconsistent
2 participants