re: Best Practice / Standard for API calls VIEW POST

TOP OF THREAD FULL DISCUSSION
re: Yup (or at least it should!) If you happen to have Go installed I've made an example package main import ( "fmt" "net/http" ) func Am...

Worth noting there's nothing in the URI spec for query to require this behaviour (it doesn't even require key=value, just that query strings are 'usually of the form key=value').

But it's definitely more conventionally used the way that @quii is describing - see for instance this on SO.

Yes it is a shame, but it is for sure the convention

Best thing to do is write a test for your server and see if the library behind it supports it. If your server supports it, you're all good and you'll hopefully make it easier for your clients

As much as I like this, I don't think Core/Linq supports this

Let me add more detail to that,

I am getting a list of Resource Parameters

FilterBy
OrderBy
etc

This is only taking in the first OrderBy parameter I send in the URL.

code of conduct - report abuse