-
Notifications
You must be signed in to change notification settings - Fork 1
Final ui and api endpoint changes #2
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
Open
codinger41
wants to merge
38
commits into
develop
Choose a base branch
from
Final-UI-and-API-endpoint-changes
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
It has all Essential files and directories needed to run the EventsManager App
Description of Task to be completed?
The UI template which is in the template directory has been completed with HTML, CSS and JS.
The Server directory has the API routes, controllers and models directory that should power up the API.
The Controller directory has 2 files- eventController and centerController. Both files are the main files powering up the API Routes.
The Models directory has dummy data for Events and Centers as welll.
The Routes directory is responsible to API routing and versioning.
How should this be manually tested?
run
Npm installto install all dependencies,run
Npm startto start the express server.To test the API, open up an API tester like POSTMAN and test these routes:
GET http://localhost/events
GET http://localhost/events/eventId
POST http://localhost/events
PUT http://localhost/events/eventId
DELETE http://localhost/events/eventId
POST http://localhost/centers
GET http://localhost/centers
GET http://localhost/centers/centerId
PUT http://localhost/centers/centerId
DELETE http://localhost/centers/centerId
Any background context you want to provide?
What are the relevant pivotal tracker stories? (if applicable)
1.Users should be able to create events, delete events and modify events.
2.Admin should be able to add centers, delete centers and Edit centers