VorTECHsa / VorTECHsa/python-sdk
dynamic column structure makes it very difficult to use the SDK in an automated form
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 25
- Forks
- 12
- Avg merge
- 20h 47m
- Merged PRs (30d)
- 2
Description
The nested data structure and the resulting dynamic columns mean that you can't just set up a standard script and expect to always work.
Recognise this is quite a difficult problem to solve and don't know of any easy way to get round it. But I think this is quite an existential question for the usefulness of the SDK. If it doesn't allow things to be automated, it won't be used at all.
Contributor guide
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
The issue does not name files, tests, or entry points. Start by locating the SDK code that builds nested data and dynamic columns, then clarify the expected stable interface for automated scripts. Done should mean users can rely on a repeatable column structure when automating SDK use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100