-
Notifications
You must be signed in to change notification settings - Fork 0
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
Implements both the user and game databases #15
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces a lot of files/code from Mozilla's Express tutorial, with the goal of having easily configurable layouts for game description pages. Tutorial: https://developer.mozilla.org/en-US/docs/Learn/Server-side/Express_Nodejs/skeleton_website
Delete all old files, ignoring database code for now. Implements a basic homepage that has a search button and input field.
Implements linking between `Homepage.js` and `Gamepage.js` using the button.
Also added button to go to the login page.
Added `databases/` to store the user data, `servers/` to modularize running the backend servers. Miscellaneous other files have been updated to reflect the changes.
Creates two new files in `src/` that define how the login page looks, and a third in a new `servers/` folder that dictates how to query the `user_info.db` database. Unlike previous front-end files, `src/Loginpage.js` is class based, and is an extension of React's `Component` class. See the file for more details. Updates `README.md` to reflect the changes.
Rewrite all of the `src/` webpages to follow the same object-oriented coding principles that `src/Loginpage.js` has, as well as convert most variables to lowercase.
* Add games database. * Update `games.db` to follow proper formatting. * Move database code out of `servers/`. Only one `.js` file is needed to maintain all databases, so `start_db.js` will suffice. Logic is now added such that the homepage search bar actually queries the games database, and outputs to console. TODO: Implement some sort of fuzzy matching for searching, as it currently only accepts case-sensitive substrings as search queries. * Update `README.md` to reflect most recent changes. Also adds TODO items that will need to be implemented later.
kylechui
added
backend
Database and backend-facing features
enhancement
New feature or request
frontend
Page layouts and user-facing features
labels
Nov 25, 2021
This was
linked to
issues
Nov 25, 2021
Closed
Updates the command for starting up the local database servers, now that `servers/` has been deprecated.
* Configured import statements in every file * Deleted random files, started working on homepage * Configured react-boostrap to gamepages * Configured navigation bar * Finished Gamepage outline * Cleaned up code added comments for everything
… a couple of places
Updates various files for bug fixes, rewrites code to be more object-oriented, and updates some code blocks for more consistent style. Front-end pages should all be extensions of the react `Component` class, and should use the `render()` method to display their contents.
Made a simple 3 column user page. Includes a section for the backlog, playthroughs, and friends list. Also includes the navbar at the top. Needs to be altered to use the database
Merge branch `reactPagesSimpleChanges` into the current branch. Adds changes to the front-ends for `Gamepage.js` and `Homepage.js`, as well as introduces new code that sets up the framework for `Userpage.js`.
Made the buttons on the home page properly spaced after that was lost in a merge Switched to using an InputGroup for the navbar so the button integrates with the textbox, and changed search buttons to be consistently green. This may have made some things off center but I can't tell, if you can please fix :)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
backend
Database and backend-facing features
enhancement
New feature or request
frontend
Page layouts and user-facing features
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The user information should be stored in a database called
user_info.db
, which includes usernames, passwords, about me's, etc. The game information is stored ingames.db
, and contains various attributes about the games.