kompot/rjanko issues and pull requests

#32 - Replace custom routing with react-router when 1.0 is released

Issue - State: open - Opened by kompot over 9 years ago

#31 - Replace baobab with redux

Issue - State: open - Opened by kompot over 9 years ago

#30 - Make admin UI use some standard UI lib

Issue - State: open - Opened by kompot over 9 years ago

#29 - Drop `forego` in favour of `node-foreman`

Issue - State: open - Opened by kompot over 9 years ago

#28 - Use `babel-plugin-react-require` plugin to never require React explicitly

Issue - State: open - Opened by kompot over 9 years ago

#27 - Use `react-hotkeys` to make using CMS a breeze

Issue - State: open - Opened by kompot over 9 years ago

#26 - Replace custom grown templating solution based on lodash with yeomaon generator

Issue - State: open - Opened by kompot over 9 years ago

#25 - Use jsonapi.org as API interface

Issue - State: open - Opened by kompot over 9 years ago

#24 - Integrate some forms solution

Issue - State: open - Opened by kompot over 9 years ago

#23 - Make all source imports absolute from project root (no `../../` and `./`)

Issue - State: closed - Opened by kompot over 9 years ago

#22 - Remove custom grown routing solution based on Yahoo stuff and transition to something react-router based

Issue - State: open - Opened by kompot over 9 years ago

#21 - Log `debug` module output to browser console

Issue - State: closed - Opened by kompot over 9 years ago

#20 - Get rid of `forego` as this should be covered by `docker`

Issue - State: open - Opened by kompot over 9 years ago

#19 - Integrate sentry/raven as out-of-the-box error tracking solution

Issue - State: open - Opened by kompot over 9 years ago

#18 - Implement server-side HMR based on `monkey-hot-loader`

Issue - State: closed - Opened by kompot over 9 years ago - 1 comment

#17 - Decide which components should be baked in and which pluggable pluggable

Issue - State: open - Opened by kompot over 9 years ago

#16 - Make all commands pluggable including basic ones

Issue - State: open - Opened by kompot over 9 years ago

#15 - Decide whether data persisting solution should be baked in or pluggable

Issue - State: open - Opened by kompot over 9 years ago

#14 - Use ansible to setup working docker environment based on docker-machine and docker-compose

Issue - State: open - Opened by kompot over 9 years ago - 2 comments

#13 - Decide whether server code should be bundled by webpack or just babel as it is now

Issue - State: open - Opened by kompot over 9 years ago
Labels: enhancement

#12 - Replace `create` command with `init`

Issue - State: open - Opened by kompot over 9 years ago

#11 - Minimize dependencies of the end project itself by maximizing those in `rjanko`

Issue - State: open - Opened by kompot over 9 years ago
Labels: enhancement

#10 - Make all development/production container/docker based.

Issue - State: open - Opened by kompot over 9 years ago
Labels: enhancement

#9 - Replace custom grown data cursor solution with something like `baobab`

Issue - State: closed - Opened by kompot over 9 years ago

#8 - Add passportjs integration

Issue - State: open - Opened by kompot over 9 years ago
Labels: enhancement

#7 - Child process is not killed after running test (server.js)

Issue - State: open - Opened by kompot over 9 years ago
Labels: bug

#6 - Make admin interface localizable from the start (react-intl)

Issue - State: open - Opened by kompot over 9 years ago
Labels: enhancement

#5 - Add basic tests + travis ci integration

Issue - State: closed - Opened by kompot over 9 years ago - 1 comment

#4 - Add code quality tools (eslint + jscs probably)

Issue - State: closed - Opened by kompot over 9 years ago - 1 comment

#3 - Make single entrypoint for logging/debugging

Issue - State: closed - Opened by kompot over 9 years ago

#2 - Create `dev` command to run app in dev mode

Issue - State: closed - Opened by kompot over 9 years ago

#1 - Add coloring to console help

Issue - State: open - Opened by kompot over 9 years ago

Ecosyste.ms: Issues

GitHub / kompot/rjanko issues and pull requests

#32 - Replace custom routing with react-router when 1.0 is released

#31 - Replace baobab with redux

#30 - Make admin UI use some standard UI lib

#29 - Drop `forego` in favour of `node-foreman`

#28 - Use `babel-plugin-react-require` plugin to never require React explicitly

#27 - Use `react-hotkeys` to make using CMS a breeze

#26 - Replace custom grown templating solution based on lodash with yeomaon generator

#25 - Use jsonapi.org as API interface

#24 - Integrate some forms solution

#23 - Make all source imports absolute from project root (no `../../` and `./`)

#22 - Remove custom grown routing solution based on Yahoo stuff and transition to something react-router based

#21 - Log `debug` module output to browser console

#20 - Get rid of `forego` as this should be covered by `docker`

#19 - Integrate sentry/raven as out-of-the-box error tracking solution

#18 - Implement server-side HMR based on `monkey-hot-loader`

#17 - Decide which components should be baked in and which pluggable pluggable

#16 - Make all commands pluggable including basic ones

#15 - Decide whether data persisting solution should be baked in or pluggable

#14 - Use ansible to setup working docker environment based on docker-machine and docker-compose

#13 - Decide whether server code should be bundled by webpack or just babel as it is now

#12 - Replace `create` command with `init`

#11 - Minimize dependencies of the end project itself by maximizing those in `rjanko`

#10 - Make all development/production container/docker based.

#9 - Replace custom grown data cursor solution with something like `baobab`

#8 - Add passportjs integration

#7 - Child process is not killed after running test (server.js)

#6 - Make admin interface localizable from the start (react-intl)

#5 - Add basic tests + travis ci integration

#4 - Add code quality tools (eslint + jscs probably)

#3 - Make single entrypoint for logging/debugging

#2 - Create `dev` command to run app in dev mode

#1 - Add coloring to console help