Add graph pattern for common query functions by corranrogue9 · Pull Request #512 · microsoft/api-guidelines
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes it sound like it's fine to ship a special purpose function because, if in the future they decide they want something more flexible, they could add it. I'm afraid that would lead to workloads using this guidance to say "I have a bunch of functions today, and might add more in the future, cause the guidance says that I can always add $filter later."
I would think that we would want to encourage workloads to move to the more general solution and not rely on exposing everything through custom functions.
| It is likewise fine to ship a handful of functions and then later ship an API that is a collection of data with a more fully-featured set of filters. | |
| While it is possible to start with one or two custom functions, you should have a plan to support a more fully-featured set of query options as the utility of your API will be significantly limited in the interim. |