(source-asana) add subtasks stream to be more complete
- Linguagem predominante
- Python
- Estrelas
- 22.1k
- Forks
- 5.4k
- Merge médio
- 5h
- PRs com merge (30d)
- 671
Descrição
### Connector Name
source-asana
### Connector Version
1.7.2
### What step the error happened?
During the sync
### Relevant information
The connector is still lacking subtasks: but including them, would allow handling Asanas data in a more complete fashion.
As Asana is a task management tool and platform, omitting subtasks would be a great loss in data completeness.
As per api spec at https://developers.asana.com/reference/getsubtasksfortask getting subtasks seems quite similar to getting tasks. There is a num_subtasks field in the tasks stream: if this is not zero, subtasks can be fetched for that entry via the api.
Since I have no development environment at hand, I am sorry I cannot try this out right now. At first sight, it seems one would just need to add the stream to https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-asana/source_asana/manifest.yaml . But would that suffice?
Best Regards 👍
### Relevant log output
```shell
```
### Contribute
- [ ] Yes, I want to contribute
---
**Internal Tracking:** https://github.com/airbytehq/oncall/issues/13259
Guia de contribuição
Direção de pesquisa
Start with airbyte-integrations/connectors/source-asana/source_asana/manifest.yaml and compare the existing tasks stream with the linked Asana get-subtasks-for-task API specification. Done means the source-asana connector exposes subtasks and includes them during sync, with the connector's available validation confirming the stream works.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- python
- Domínio
- data-engineering
- Tipo de issue
- Funcionalidade
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Pouca atividade
- Clareza
- Razoavelmente clara
- Facilidade para iniciantes
- 68/100