alex-saunders / npm-ui Goto Github PK

Bug or Feature?

Feature

Current Situation

Currently, when running the app in development mode, the app will read in project info (scripts, dependencies etc.) from this directory as it simply reads the closest package.json

Intended Change

It would be nice to be able to simulate the app being ran in another location/directory (passing the location as a parameter to npm run dev for example)

Bug or Feature?

Bug

Current Situation

In package.json, babel-preset-env is listed as a dependency, but es2015 is used in .babelrc.

Intended Change

Update .babelrc to use the new env preset.

To complete this, the following needs to be done

• Update .babelrc

Bug or Feature?

Bug

Current Situation

Current styles are quite all over the place and a lot of hacky overrides of the styles provided by the rmwc components.

Intended Change

Would be good to have much more structured styling. Would need to discuss what approach would be best to approach, e.g. styled components, css variables, sass etc.

Bug or Feature?

Feature

Current Situation

No code formatting guide is defined

Intended Change

Choose a code formatting guide.

To complete this, the following needs to be done

The project will have a lot of contributors and set a default code formatting guide could be very useful.

Pros:

• Everybody should write in the same way
• Pull request doesn't include code style guide diffs.

My proposal is to use prettier.

Bug or Feature?

Feature

Current Situation

Can only run the app in dev mode

Intended Change

A build process needs to be created for deploying the app as a dist version and that may be installed by npm i npm-ui -g and can then be opened from any directory (e.g. using npx npm-ui)

Bug or Feature?

Feature

Current Situation

At the moment no tests have been created and no test framework has been decided on

Intended Change

Decide on a testing framework and create some tests for components

To complete this, the following needs to be done

• Decide on a testing framework
• Create some initial, critical tests
• Ensure PRs pass all tests before being submitted

Bug or Feature?

Feature

Current Situation

Redux files for the feature aren't in the feature folder.

Intended Change

Move, like we did in #9, we should move the redux files into the feature folder to make the feature folder compact with their files.

What do you think?

ps: If you don't understand I can explain better.

Bug or Feature?

Feature

Current Situation

The packages view is currently empty

Intended Change

After #2 has been completed, it will need to be possible to be able to remove dependencies/packages

To complete this, the following needs to be done

• add remove dependency button to each item in the dependencies list
• add functionality to this button

Bug or Feature?

Feature

Current Situation

Currently you can just view scripts from package.json and run them

Intended Change

It would be good to be able to add and remove scripts from package.json as well

Bug or Feature?

Feature

Current Situation

The packages view is currently empty

Intended Change

On the right hand column of the packages view, you should be able to search for packages (using algolia's npm-search) and then add a dependency to the project

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

Bug or Feature?

Feature / Refactor

Current Situation

The folders structure is a little bit confusing for me.
Because there is no hierarchy and could be not enough scalable.

Intended Change

I will propose a different structure with a PR like a proposal 🙂

Bug or Feature?

Feature

Current Situation

Currently the packages view is empty

Intended Change

This view should be populated with a list of currently installed packages on the left hand column