Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Question] Default value option.

Open
#253 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
api

Research direction

Start by tracing how openapi-core applies schema default values during PATCH request validation, using the OpenAPI schema handling and request-validation entry points. Check whether configuration already distinguishes POST and PATCH behavior; done means providing a documented way to suppress defaults for omitted PATCH fields, with coverage for the reported shared-schema case.

Written by the indexing model from the issue text.

Description

We are using same schema for POST & PATCH and we declared a default value for a field. In the PATCH request, if this field is not given it is appended with default value by openapi-core. I know it should be the behaviour, but is there any way to turn this off ?

Dominant language
Python
Stars
368
Forks
140
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python-openapi/openapi-core

All issues in python-openapi/openapi-core

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.