AllenInstitute / AllenInstitute/vis
Idea: Become a backend for Flint
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 1
- Avg merge
- 10h 24m
- Merged PRs (30d)
- 7
Description
Microsoft has a new AI-friendly chart format, could be interesting to make vis a backend for it:
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
Start with the Flint chart documentation linked in the issue and review vis's existing visualization capabilities. Define what it means for vis to be a Flint backend, including the supported chart data and expected output, before locating implementation files. Done should be a clearly scoped, working Flint integration with acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100