collective / collective/sc.contentrules.groupbydate
the content type must honor workflow and permissions of parent container
- Dominant language
- Python
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
we have 2 use cases here: internet and intranet: on internet we will be probably using the default publication workflow, so we must publish directly the intermediate containers; on intranet we will have to honor the workflow and permission of the parent container.
we need to figure out how to do it and how to test it.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the content-rules action that creates the intermediate containers and reviewing any existing tests. Clarify the expected workflow and permission behavior for both internet and intranet use cases, then define tests that distinguish publication under the default workflow from inheritance from the parent container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100