delight-im / delight-im/PHP-Temporal
final class vs interface
Open
enhancement
- Dominant language
- PHP
- Stars
- 13
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Looking a the codebase I have to wonder why creating final classes that only contains constants instead of interfaces.
Something along these lines:
```php
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Start by reviewing the current final classes and their constants, then assess whether interfaces would preserve compatibility for existing users. Done requires a settled choice between one combined interface and several smaller interfaces, plus an agreed backward-compatible migration plan.
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
- 25/100