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

Asynchronously delete skills #7

Merged
merged 9 commits into from
Nov 2, 2014
Merged

Asynchronously delete skills #7

merged 9 commits into from
Nov 2, 2014

Conversation

tannerwelsh
Copy link
Contributor

This branch satisfies the requirements for release 1.3.0:

  • User can delete skills on the résumé show page
  • Deleting skills occurs asynchronously
  • Deleted skills are removed from the page without refresh

This release also makes improvements to the underlying architecture of the application, including the following changes:

  • Use RESTful routing conventions
  • Logging in skills.js
  • Format of HTML and JavaScript more consistent

In addition, the /resumes/edit page has been changed to /users/edit and now contains only a form to edit the user profile. This change removes redundancy in editing other resources.

RESTful routes are a way to implement a conventional and standardized
design to server routes that work with resources. In this case, the
resources we're working with are `jobs` and `skills`, so the routes that
affect those resources should follow RESTful conventions.

There are two significant changes in this commit:

1. When working with singular resources, add an identifier to the URL
   (e.g. DELETE /jobs/21 means "delete job resource with id 21)
2. Let the HTTP verb define the route (e.g. PUT /jobs/21 means
  "edit job resource with id 21, no need for an extraneous /jobs/edit in
  the route)

Check out
http://en.wikipedia.org/wiki/Representational_state_transfer#Applied_to_web_services
for more information
Partials don't include the <li> context for skills, which makes them
match the structure of how jobs are managed.
Adds a delete button to skills on the résumé show page so that user can
remove skills as needed
Since jobs can be edited on the main page, and skills can be created and
deleted, making them editable on a separate page seems redundant.

So instead there will just be a separate edit page for the user profile
information.

Now the app has two primary pages:

- "/" which points to "/resumes/show"
- "/users/edit"

This commit also removes the "put /skills/:skill_id" route, as it is no
longer in use anywhere.
Reduce smaller functions, add extra comments.
tannerwelsh added a commit that referenced this pull request Nov 2, 2014
@tannerwelsh tannerwelsh merged commit 65c95b1 into master Nov 2, 2014
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.

1 participant