singer-io / singer-io/tap-github
Teams schema is incorrect
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
The current schema has the following property:
{
"type": [
"null",
"object"
],
"properties": {
...,
"parent": {
"type": [
"null",
"string"
]
}
}
}
When it should be:
{
"type": [
"null",
"object"
],
"properties": {
...
"parent": {
"type": [
"null",
"object"
],
"properties": {
"description": {
"type": [
"null",
"string"
]
},
"html_url": {
"type": [
"null",
"string"
]
},
"id": {
"type": [
"null",
"number"
]
},
"members_url": {
"type": [
"null",
"string"
]
},
"name": {
"type": [
"null",
"string"
]
},
"node_id": {
"type": [
"null",
"string"
]
},
"permission": {
"type": [
"null",
"string"
]
},
"privacy": {
"type": [
"null",
"string"
]
},
"repositories_url": {
"type": [
"null",
"string"
]
},
"slug": {
"type": [
"null",
"string"
]
},
"url": {
"type": [
"null",
"string"
]
}
}
}
}
}
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
Locate the Teams schema definition in the tap-github repository and inspect the parent property. Update its type and nested properties to match the schema shown in the issue, then run the repository's relevant validation or test command to confirm the corrected schema accepts the expected object structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100