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

Remove JaResource/Canary from RoleController #1000

Conversation

landongrindheim
Copy link
Contributor

@landongrindheim landongrindheim commented Oct 1, 2017

What's in this PR?

Remove reliance on JaResource/Canary in RoleController

References

Closes #901

Progress on: #864

@spec create_changeset(Codecorps.Role.t, map) :: Ecto.Changeset.t
def create_changeset(struct, params \\ %{}) do
changeset(struct, params)
end
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see you did the same across several PRs. Sorry for not reviewing earlier and saving you some time, but I think it would be preferable to revert on this and simply call Role.changeset from the controller instead.

@landongrindheim landongrindheim force-pushed the 901-move-role-controller-from-ja-resources branch 2 times, most recently from 2e792d3 to 02899a0 Compare October 3, 2017 13:50
@landongrindheim landongrindheim force-pushed the 901-move-role-controller-from-ja-resources branch from 02899a0 to a82fe9a Compare October 3, 2017 13:55
@landongrindheim
Copy link
Contributor Author

@begedin Updated!

Copy link
Contributor

@begedin begedin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@begedin begedin merged commit de0bbf7 into code-corps:develop Oct 3, 2017
@landongrindheim landongrindheim deleted the 901-move-role-controller-from-ja-resources branch October 10, 2017 08:00
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.

2 participants