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.
[Pivotal Tracker Link][tracker]
What this PR does:
This pull request implements part of the backend for PD model and PD registrations. It did NOT yet add the database migrations, as there is no testing for anything yet.
How should this PR be tested?
Rspec and Cucumber after figuring out how everything connets.
Did not account for admin backend control yet, as in PD registrations logistics are not fully setup yet.
Are there any complications to deploying this?
No database migration or testing added yet.
Checklist:
michael/12345-add-new-feature
Any branch name will do as long as the story ID is there. You can usegit checkout -b [new-branch-name]
)