-
Notifications
You must be signed in to change notification settings - Fork 356
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
RESTful conversion potential leftovers/bugs #6307
Comments
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the traige process documentation. |
@himdel Are these still issues? |
Potentially, yes. As long as we have restful and non-restful controllers, this can be a problem. We should convert (use |
@kavyanekkalapu do you know if we made any progress on these? |
@chessbyte I don't think so. I can see restful_routed? for sure in code. need to search remaining paths. |
This issue has been automatically marked as stale because it has not been updated for at least 3 months. If you can still reproduce this issue on the current release or on Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation. |
These places redirect to
show
w/o checking if the target controller is restful. See ManageIQ/manageiq#10020Each of these places needs to be revisited and checked to see if the target controller might be restfull. In such case a restful route needs to be used.
This issue was moved to this repository from ManageIQ/manageiq#10021, originally opened by @martinpovolny
The text was updated successfully, but these errors were encountered: