-
Notifications
You must be signed in to change notification settings - Fork 26
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
Add delete endpoint for portfolio_item #84
Add delete endpoint for portfolio_item #84
Conversation
cc - @lgalis |
delete "/api/v0.0/portfolio_items/#{portfolio_item_id}", :headers => admin_headers, :params => valid_attributes | ||
end | ||
|
||
it 'deletes the record' do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@syncrou Do we need a TODO to add a test as a non admin user it should fail. Since we don't have any constraints check now we would have to wait. Also a GitHub issue might help
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a TODO that points to this Issue: #85
parameters: | ||
- $ref: '#/parameters/PortfolioItemID' | ||
responses: | ||
204: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@syncrou The 204 status reads
The HTTP 204 No Content success status response code indicates that the request has succeeded, but that the client doesn't need to go away from its current page
@lgalis Is the UI going to react properly for a 204, it would have to issue a refresh of the portfolio items page
51e8289
to
1786516
Compare
@syncrou - looks good |
Use PF4 data list to show orders.
No description provided.