iamao / react-raise Goto Github PK

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently the project does not generate a package.json file

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

After setup information have been collected, a package.json file should be generated using that information

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature, bug

What is the current behavior?

Currently there is no way for react-raise to know the base directory in order to create files in the project directory.
What it does instead is create the project inside react-raise folder

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

It should get the current base directory and create project in that directory

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

currently I can only create a new react application

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

I should be able to create a new component by typing something like:
$ raise component -C Dashboard

• where -C is connected. i.e I intend to make Dashboard a container component. It then generates Dashboard and connects it to the redux store
• Dashboard is the name of the component
• if -C is not provided then it is a presentational component by default

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

There is no sample webpack config to follow

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

There should be a sample webpack config file to build from

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently the command just generates empty files

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

It should populate generated files with a sample template
for example if generating a react component, it should add the following template:

import React from 'react';

/**
 * Home view of the project
 * @class
 */
class Home extends React.Component {
  
  /**
   * render lifecycle of the component, 'renders' the component
   * to the DOM.
   * @returns{Object} react component to render
   */
  render() {
    return (<h1>Home</h1>);
  }
}

export default Home;

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature and bug

What is the current behavior?

Currently generated files are empty

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

Generated files should have a starter template in them.
If a file like Home.component.js is generated, then it should contains something along the lines of:

import React from 'react';

/**
 * Home view of the project
 * @class
 */
class Home extends React.Component {
  
  /**
   * render lifecycle of the component, 'renders' the component
   * to the DOM.
   * @returns{Object} react component to render
   */
  render() {
    return (<h1>Home</h1>);
  }
}

export default Home;

In this case all that I need to do is add my own methods and implementations.

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature & Bug

What is the current behavior?

Currently it just installs express and its dependencies when a user selects to use with express

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

It should set up a basic express server when the use chooses so.

• It should use the port 7000 on local
• It should serve static files at '/dist/'
• It should be integrated with webpack-dev-server

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently there are no continous integrations

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

Continous integrations should check for code breaks and code quality

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

There is no way to build the actual folder structure from the schema provided

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

There should be a way to render the folder schema structure provided
For example, if the schema provided is:

{ src: [
    { actions: ['index.js'] }
  ] 
}

Then it should create a file structure like:

/app
    /src
        /actions
            index.js

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

feature

What is the current behavior?

Currently react-raise has no definite structure to use to create a react file structure

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

There should be a consistent file structure that react-raise will use to render and generate a new react application
Example:

{ app: [
  {
    src: [{
       components: [...],
       'index.js'
    }]
   //...
  ]
}

Where the object keys that are arrays are folders and strings are files.

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

Do you want to request a feature or report a bug?

Chore

What is the current behavior?

Currently the documentation is very limited

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

What is the expected behavior?

The documentation should be split into two:

• For users:
  • Doc should cover installation and setup process
  • Doc should cover use cases
  • Doc should contain plenty of clear examples
• For developers:
  • Doc should cover setup process
  • Doc should cover startup process
  • Doc should cover contribution guides

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

A .babelrc file is currently not generated

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

After user answers setup questions, a .babelrc file should be generated
using the presets:

• stage-2
• es2015
• react

And the plugins:

• transform-object-rest-spread,
• transform-decorators-legacy

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently there is no compiled list of dependencies

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

There should be a list of dependencies that will enable react-raise to create a package.json that contains those dependencies

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently there are no dependencies for the express server

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

It should have dependencies for express in case the user wants to build with express server

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

feature

What is the current behavior?

Currently there are no code linters in the project

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

• eslint should check for coding style locally
• houndCI should review and comment on open PRs

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently the project does not handle any cli argument

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

Command line arguments should be parsed.
For example, if I type:
$ raise new app
Then it should know I wish to create a new react application
List of cli args:
new - create new react app
component - create new component
action - create new action
reducer - create new reducer
test:e2e - create new e2e test spec
test:component - create new component test spec
test:action - create new action test spec
test:reducer - create new reducer test spec

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Bug

What is the current behavior?

Currently I can type anything as my main entry file. It should not be so

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

I should only be allowed to use javascript files as my main entry in package.json.
If i type in something without a js extension then I should get an error
or better yet if it should append the .js for me.

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently it show nothing

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

It should render a graphical 'React Raise' on start up

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently, a webpack config file is not generated

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

A webpack.config.js should be auto generated with information from the webpack smple config.

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently the only way to start react-raise is by navigating to the directory and run:
$ node index.js

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

I should be able to create a react app in any directory on my filesystem by running a command.

• I should be able to create a new react application by running: $ raise new <app name>
• I should see a list of all available commands by running: $ raise --help or $ raise -h
• I should see the version by running $ raise -v or $ raise --version

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently nothing happens when a user starts the command

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

It should prompt me for the following questions:

1. Description of my app(optional)
2. My name(optional)[so it can add the author field in package.json]
3. Main entry of app(Default: index.js)
4. License(Default: MIT)
5. Initialize with express(y/n)

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification

Do you want to request a feature or report a bug?

Feature

What is the current behavior?

Currently nothing happens when you pass in the new argument

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via https://jsfiddle.net or similar (template: https://jsfiddle.net/84v837e9/).

N/A

What is the expected behavior?

A new react app and structure should be created if I pass in new as the first argument
I.E if i type:
$ raise new awesome-app
Then I should get a bootstrapped react application

Which versions of react-raise, and which browser / OS are affected by this issue? Did this work in previous versions of react-raise?

N/A

NB: You can drop a comment below for more clarification