Implement membership rename across schema, ORM, APIs, and tooling - #43
Merged
Conversation
- Added execution order documentation for the membership rename process. - Created summary and detailed plans for schema migrations, ORM entities, services, API usages, and E2E tooling. - Replaced `user_trust_settings` with `user_membership` in the database schema and updated related ORM entities and services. - Updated API middleware and management API to reflect the new membership structure. - Implemented local development seeding for the new membership model and adjusted E2E tests accordingly. - Ensured cumulative verification steps are documented for operator execution. This commit completes the transition from trust settings to a dedicated membership model, ensuring no legacy references remain.
Member
Author
|
/test |
✅ CI PassedAll checks completed successfully.
|
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.
user_trust_settingswithuser_membershipin the database schema and updated related ORM entities and services.This commit completes the transition from trust settings to a dedicated membership model, ensuring no legacy references remain.