Skip to content

Use per-entity criteria to lock public or published entities from update#830

Merged
yuanzhou merged 13 commits intodev-integratefrom
karlburke/LockPubEntitiesFromUpdate
Apr 4, 2025
Merged

Use per-entity criteria to lock public or published entities from update#830
yuanzhou merged 13 commits intodev-integratefrom
karlburke/LockPubEntitiesFromUpdate

Conversation

@kburke
Copy link
Contributor

@kburke kburke commented Mar 27, 2025

Add second entity validator to check if entities are "locked" by some criteria before allowing an update.

@kburke kburke requested a review from yuanzhou April 2, 2025 13:50
kburke and others added 4 commits April 3, 2025 09:07
…Strip validate_application_header_before_entity_create from all before_entity_update_validator entries. Comments added for clarity. Consolidate entity validator args to one dict. Remove block on modifying public Collections from previous Issue, so now blocked by new validator and block can be overridden.
@yuanzhou yuanzhou merged commit bd4b01b into dev-integrate Apr 4, 2025
5 checks passed
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.

2 participants