This repository was archived by the owner on Jun 20, 2025. It is now read-only.
Open
Conversation
…argument to work with guard.
…guard on Manage Data permission for replaced files
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
@kevinmershon this is ready for review although setup to test will take awhile. You will need to create a client, a user, access_levels and user_access_levels. As we've discuss client_metadata rows are soft deleted but I've added a
deleted_bycolumn to keep a record user who deleted the row. The update method soft deletes the current client_metadata by key_name and adds a new row with the same key_name but with the new value. A constraint exists to allow only one non-deleted key_name row per client_id.