在imi3.0中建议增加框架命名的Exception
Open
Nobody has claimed this yet.
3.0
optimization
- Dominant language
- PHP
- Stars
- 1.2k
- Forks
- 169
- PR merge metrics
- No merged PRs in 30d
Description
- 我的问题、建议：（必填）
个人建议在3.0 中可以增加框架命名的Exception
比如一个基类Exception：命名为 ImiBaseException
然后比如像CacheManage中可以增加 ImiCacheException错误类
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 names no files or tests and proposes a framework-wide exception design for imi 3.0, including ImiBaseException and an ImiCacheException for CacheManage. Start by locating the existing exception structure and CacheManage implementation, then confirm the intended scope with maintainers; done means the agreed named exception hierarchy is implemented and covered by the relevant checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100