ProfessionalWiki / ProfessionalWiki/Rules
Use registry for condition and action types
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- PHP
- Stars
- 3
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
Contributor guide
No contributing guide indexed for this repository
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
The issue body names no files, tests, or entry points. Start by locating the condition and action type definitions and their registration or lookup code, then determine the intended registry design with project context. Done means both types are resolved through a registry and existing behavior remains covered by the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100