Consider deprecating old validation API
Open
enhancement
- Dominant language
- Shell
- Stars
- 2
- Forks
- 5
- PR merge metrics
- PR metrics pending
Description
**Feature request**
It would be great to have logging for api.
**Use case**
Many users need this functionality for production deployments.
**Implementation idea**
Add a new config option `enable_logging` with default `false`.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or an entry point, and its title about deprecating validation conflicts with the body’s request for API logging. Start by locating the API configuration and validation code, then determine the intended scope; the requested outcome is an `enable_logging` option whose default is `false`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100