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

Does it support defining default (optional) fields?

Open
#14 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by checking the current serializer behavior with the AVRO schema shown in the issue, including an omitted field and a null value. Done means determining whether optional fields with null defaults are supported and, if not, defining the required behavior before identifying the relevant implementation and tests.

Written by the indexing model from the issue text.

Description

Hi, I am trying to understand if the current version supports defining optional fields.

Like this

 {
    "name": "username",
    "type": [
      "null",
      "string"
    ],
    "default": null
  },
Dominant language
Python
Stars
135
Forks
43
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 linkedin/python-avro-json-serializer

All issues in linkedin/python-avro-json-serializer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.