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

Correctly configure custom attributes for DELETEs #14751

Merged

Conversation

imtayadeway
Copy link
Contributor

@miq-bot
Copy link
Member

miq-bot commented Apr 12, 2017

Checked commit imtayadeway@a9048af with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks good. 👍

@abellotti
Copy link
Member

Thanks @imtayadeway for this bug fix. Don't we need a test for the custom attribute DELETE ?

@imtayadeway
Copy link
Contributor Author

@abellotti there is already a test for this!

This is relying on legacy behavior whereby if you have the DELETE method enabled and don't have an action configured it will do the default thing. IMO this is an issue too but I think the described issue is best fixed this way and we can look into that with a follow up

@abellotti
Copy link
Member

👍 Thanks. 🎵

@abellotti abellotti merged commit 7aa1e78 into ManageIQ:master Apr 13, 2017
@abellotti abellotti added this to the Sprint 59 Ending Apr 24, 2017 milestone Apr 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants