alex-saunders/npm-ui

Split up the Scripts container into its component parts

Open

#17 opened on Jan 9, 2018

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (2 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (11 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Bug or Feature?

Feature / Improvement

Current Situation

The Scripts container is getting big as all functionality for the entire view is contained within this container.

Intended Change

We should split up the container and create components for its various parts, to held separate out concerns. The container should simply connect to the redux store and pass properties/functions down to its children, there should be little more functionality than that for the container.

To complete this, the following needs to be done

  • Create components for the container's various parts
  • Pass redux store properties/dispatch methods down to these components
  • Ensure components have the correct functionality

Contributor guide

Research direction
Identify the current Scripts container's responsibilities and split them into separate components, then connect each to the Redux store via props.
Tech stack
javascript
Domain
desktop
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ReactReduxJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65