singer-io / singer-io/tap-github
Issue assignee has no properties
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 76
- Forks
- 86
- PR merge metrics
- No merged PRs in 30d
Description
In the issues schema, there is an assignee field of type object but it has no properties. This causes an error with bigquery taps because the schema for json has to be defined (in postgres, it just accepts a json blob).
Is this intentional or incomplete? I'm happy to open a PR. Is there a way to reuse assignee.json ?
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 in tap_github/schemas/issues.json at the assignee field referenced in the issue, then compare it with assignee.json. Determine how the issue schema should represent assignee data and verify that the resulting schema is accepted by BigQuery taps without changing the PostgreSQL behavior.
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
- 48/100