Skip to content
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

Revert "Fix "Create profile" page not supporting dark mode (#8110)" #9201

Merged
merged 1 commit into from
Dec 23, 2024

Conversation

Weiko
Copy link
Member

@Weiko Weiko commented Dec 23, 2024

Reverts #9185
This PR breaks sync-metadata, not supporting defaultValue changes with TEXT type. Will merge back after 0.35

@Weiko Weiko merged commit c947040 into main Dec 23, 2024
13 checks passed
@Weiko Weiko deleted the revert-9185-fix/8110-new-user-dark-mode branch December 23, 2024 13:11
Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

PR Summary

This PR reverts dark mode support changes for the "Create profile" page and workspace member default color scheme due to sync-metadata functionality issues.

  • Changed default colorScheme from 'System' to 'Light' in /packages/twenty-server/src/modules/workspace-member/standard-objects/workspace-member.workspace-entity.ts
  • Reverted dark mode support in /packages/twenty-server/src/engine/core-modules/user-workspace/user-workspace.service.ts createWorkspaceMember method
  • Changes will be re-implemented after version 0.35 to resolve sync-metadata compatibility issues

2 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile

samyakpiya pushed a commit to samyakpiya/twenty that referenced this pull request Dec 28, 2024
…8110)" (twentyhq#9201)

Reverts twentyhq#9185
This PR breaks sync-metadata, will merge back after 0.35
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.

1 participant