Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coreys branch #1

Open
wants to merge 43 commits into
base: master
Choose a base branch
from
Open

Coreys branch #1

wants to merge 43 commits into from

Conversation

devspacenine
Copy link
Collaborator

Ok, I tried to break it up into logical commits as best I could. Just start from the oldest commit and make your way towards the latest. There are a couple of commits that were just for little bug fixes or tweaks. Don't dwell too much on those.

I'll try to add some github comments to help clarify some things.

…ES7/JSX code to valid ES5 and bundling CSS/JS
…act-Router SPA routing and a Redux wrapper for global state management
…browsers local storage so it persists even after a session expires
… by an action creator method) and determine how the redux state should be updated
… Also created a fabfile for scripting tasks.
@devspacenine
Copy link
Collaborator Author

Looking at split diffs will probably be more helpful than the unified ones, since most of the edits were additions.

players = require('./libs/data/players'),
swig = require('swig'),
app = express(),
port = 8080;

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its a good practice to chain your declarations as long as you can. Something about how v8 does optimization.

@devspacenine
Copy link
Collaborator Author

dev-ui

@chrislbs
Copy link
Owner

So, I feel like this is just too much stuff to bring in from the get go. Not that all of it isn't valuable. Largely this project is for me to learn some of this new technology stack. I'm not intending on doing any complicated css work at the moment. I was intending on just bring in the http://getskeleton.com/ css library to just do some basic stuff. I'm not sure if I want to bring in a css framework that compiles down to a single css file when I'm largely just wanting to display a single grid on a page.

I'd really just like to have a vanilla react application for the front end. Maybe use one of the build tools to generate a single js file to serve to the page.

I'd like to boil this down to just basic react, babel for es6 transpiling, and perhaps a build tool that will create a single javascript file for the entire application.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants