-
Notifications
You must be signed in to change notification settings - Fork 57
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
DELETE method #20
Comments
• Add FSNRequestMethodDELETE to the FSNRequestMethod enum. |
@gwk Why not list methods as String Constants! |
@sugarmo that might have been a better approach. At the time I chose to use the enumeration to ensure that each supported HTTP method was completely implemented; we only used GET and POST at the time. I guess that the downside of using strings is there are more ways to make an invalid or nonstandard request. The real question is, if FSConnection was changed to use string methods, which of methods would require additional logic? If they all just work then I agree it would be a good option, but then again, in that case it is trivial to add the enums. I never added the others because I never had endpoints to test them on. |
@gwk I think the validity of a HTTP method should not be considered by an open source network library. A library should ensure that users can use it in most cases without modifying source code. And I think that if you change to use string constants, you will have not much thing being rewritten. |
@sugarmo thanks again for the input. i have not worked on FSNetworking for quite some time, and have no plans to make these changes, nor do I have commit access to the original github repo. However if you would like to create a fork I would be happy to review changes and discuss. |
My backend has a DELETE endpoint. What needs to be changed for this library to support DELETE requests?
The text was updated successfully, but these errors were encountered: