Welcome to Yieldbot! Here is a working example project we'd like to see you work with to show some of your work changing around this codebase.
- Modified users route to limit DB query to to just the requested range, rather than wasting cycles retrieving the whole database and filtering down.
- Added two routes to retrieve users in a range pre-sorted by name; usersAscendingSort and usersDescendingSort.
- It may be possible to reduce creating 2 routes for each column you might want to sort by using a call route instead of get. (Researching)
- Implemented and expandable function getSortedUsers to index and sort the database then pulling out just the rows in the requested range.
- Added route users.length to get the current number of rows in the DB.
- Modified usersById to handle users that are not found by filling in all fields with a null value.
- Added route offices to retrieve the office address of the specified office names.
- set(usersByName) route added but complications have been encountered getting it work as expected:
- Falcor magic automatically does an ascending sort to the incoming JSON which in and of itself is not an issue but if you pass:
only the user's company comes through and if you remove the company only their email comes through, etc.{ json: { usersByName: { 'Aimee Farmer': { is_enabled: true, name: 'Aimee Farmer', company: 'TELLIFLY', email: 'aimeefarmer@tellifly.com', phone: '(823) 547-2743', office: 'Portland' } } } }- Currently bulkDocs is not updating the database even when a new value is coming through, correcting the code to update the database has been put on the backburner since all expected data is not even getting to the route.
- Fixed a bug that was causing getSortedUsers to return more results than requested.
- Fixed a bug when using a page number link next or previous would both start over from page 1 because the currentPage was being stored as a string.
- Added buttons to test functionality of 4 routes get(users), get(usersAscendingSort), get(usersDescendingSort), get(offices)
- get(offices) currently just outputs the stringified JSON as a method has not yet been added to display the data in a meaningful way
- Added pagination support.
- Currently restricted to ascending or descending sort of the name column while a sustainable solution is being researched for the API layer.
- All calls were broken out in to individual functions so that the site would not need to be recompiled in order to test each API call.
- Added a single call to handle getting sorted users, it determines if we are ascending or descending and calls the correct function.
- Added CSS to force the links to behave like links
- Set color to blue
- Set cursor to pointer or hand (to cover all browsers) added cursor: hand to .header .cell:hover as well.
- Set text decoration to overline underline to make it stand out.
- Put pagination links in a div and floated it right.
- Modified CSS to alternate background color of table rows.
- Adding a call route "sortedUsers" that will allow granular control over which column the client wants the data presorted by.
- This is currently in a state of built but regardless of the setup we either get back an HTTP 500 or an empty jsonGraph.
- Adding a set route "usersByName" that will allow the client side to update records and could easily be expanded to add new records.
- This is currently about 90% complete with calls coming in but each user only has 1 key value pair and assuming this wasn't a problem the update DB code is not updating the DB
- If we could get call routes working this might be a prime candidate for converting to a function.
- Make office names clickable and have the test in that cell replaced by the office address.
- Clicking on the address should either link to google maps or a link should be included, in parenthesis, as part of the text replacement.
- Add a dropdown to set number of rows per page.
- Better understand webpack then see if it can be optimized
- Example: currently the hot server does not sync CSS.
- Fix table to not extend full width if it isnt needed.
- Wrap it and pagination in a div so the pagination links never extended beyond the right boarder of the table.
- Potentially stand up a POC using GraphQL + relay to truly determine which would be the better prod solution for our dataset.
- Try to optimize users.length route
- Hopefully we do not need to retrieve all docs in order to get a row count.
- Remove debug logging.
- Vagrant
- Virtualbox
- git
- 2 cpu (cores) and 2GBs of RAM to dedicate to the vagrant VM.
git clone https://github.com/kenjindomini/pancake_project.git ~/pancake_project # If on windows be sure to use powershell which supports some *nix conventions like ~ and ls
cd ~\pancake_project # Verify you see project files like README.md if not you will likely see a directory named pancake_project cd in to that as well
vagrant up # This will take a few minutes, grab your beverage of choice and/or have a promenade around the lake.
vagrant ssh # On windows be sure the full path to Git\usr\bin is in PATH as this will contain ssh.
cd pancake_project # Verify you see project files like README.md if not you will likely see a directory named pancake_project cd in to that as well
npm run start
- Node + npm
- Python 2.7.2
- git
git clone https://github.com/kenjindomini/pancake_project.git ~/pancake_project # If on windows be sure to use powershell which supports some *nix conventions like ~ and ls
cd ~\pancake_project # Verify you see project files like README.md if not you will likely see a directory named pancake_project cd in to that as well
npm install # get dev and app dependencies
npm run build-dev # first time setup for local development (Will not work on windows due to joining commands via &&.)
npm run start # run webpack dev server and thin backend server
Note: if your server supports apt-get you could download the two shell scripts from the repository:
- ./prereqs.sh # Will perform apt-get install -y build-essential libssl-dev git python2.7 and install NVM with 4.1.1 as the default node version
- ./autodev.sh # Will do git clone, cd you in to the clone, run npm install, and npm run build-dev
- npm run start
Completed features were confirmed working on the following versions of node:
- 4.2.0
- 4.1.2
- 4.1.1
- 4.0.0
- Application breaks on version below 4.0.0 (updated package.json)
- 0.12.7 (failed)
- 0.10.40 (failed)
Note: Did not test any version labled iojs.
In case the newer syntax is throwing you for a loop.
https://github.com/addyosmani/es6-equivalents-in-es5
Because it can be a little odd until understood.