BeaconCMS / BeaconCMS/beacon_live_admin
Display the subject/agent who triggered a revision
- Dominant language
- JavaScript
- Stars
- 73
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
Publishing a page or layout creates a new revision but we don't store "who" performed such action. Users can define their own authz/authn rules providing the agent that's current logged in or the system that's performing actions, so we need to store that agent as metadata on the revision so we can display it on the interface.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the publishing flow for pages and layouts, then locate the revision data and the authentication or authorization agent available during those actions. Inspect the revision display in the interface; done means newly created revisions retain the triggering agent as metadata and show it to users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, javascript
- Domain
- authentication, authorization, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100