Some components should not be writable when meeting is closed
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 2
- Forks
- 0
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 1
Description
- ActiveCheck
- Like-buttons
etc...?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the ActiveCheck and Like-buttons components and reviewing how they handle writes when a meeting is closed. Clarify which other components are included by “etc...?” and define the expected blocked behavior. The work is done when all agreed components are non-writable after closure and the relevant behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100