Validator option
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files or tests. Start by locating the existing Bind and Validate entry points, then review how a configurable default validator could fit the proposed API. Done means the scope and configuration behavior are agreed, implemented, and covered by tests.
Written by the indexing model from the issue text.
Description
Why not add Validator option, but not inside the code, only a default struct that after each one can config with the validator that want.
Like:
render.Validator := &DefaultValidator{...}
....
and after use something like:
render.Validate(...)
or something inside de Bind.
What do you think?
- Dominant language
- Go
- Stars
- 340
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from go-chi/render
-
Render and Bind panic on unexported nested interface fieldsPossibly taken @duongynhi000005-oss claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Channel response appends JSON null after context timeoutPossibly taken @awais-ur-rehman claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
Any concern render.JSON() can leak internal errors to outside?Possibly taken @team-humaki claimed this 50 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
WriterSetTimes: the UTIME_NOW check fails when the kernel uses its coarse clockPossibly taken @JakeChampion claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JakeChampion/lang#14224 ·
Maintainers usually reply within 1 day
-
agent-butler-finding bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jordansmall/spindrift#6391 ·
Maintainers usually reply within 1 day
-
common.Retry: data race on the shared response/err variables when the request context ends mid-attempt (v65.127.0, v65.128.0)Possibly taken @kmohit00 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oracle/oci-go-sdk#676 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
SAP/crossplane-provider-btp#1175 ·
Maintainers usually reply within 1 day