AllenInstitute / AllenInstitute/vis

React Components

Open
#130 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
10
Forks
1
Avg merge
10h 24m
Merged PRs (30d)
7

Description

Is your feature request related to a problem? Please describe.
No.

Describe the solution you'd like
Add React components to a new NPM package with learnings from creating the examples.

Describe alternatives you've considered
N/A

Additional context

  • How should we handle providers?
  • Create vis-react package
  • Omezarr Component
  • DZI Component
  • Scatterbrain Component
  • Publish package
  • Embedded code editor or link to a codepen?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. First clarify the scope of the proposed vis-react NPM package: provider handling, Omezarr, DZI, and Scatterbrain components, publishing, and examples or CodePen; then define acceptance criteria for each deliverable.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.