linkedin / linkedin/python-avro-json-serializer
Does it support defining default (optional) fields?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 135
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I am trying to understand if the current version supports defining optional fields.
Like this
```
{
"name": "username",
"type": [
"null",
"string"
],
"default": null
},
```
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
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.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100