Open anallely opened 9 years ago
Currently I have a resource
v1/catalog
and the generated methods are like
getCatalogAndSizeAndFrom
This name sounds no very comprehensive.
And Option would be getCatalogBYSizeAndFromAnd.... but this could be no convenient for resources like v1/catalogById/${id}
because it would generate getCatalogByIdBySizeAndFrom :S This sounds not very cool
So a better option would be using WITH first
For example CatalogByIdWithFromAndSize(0,20)
I think using "where" is clearer, i.e.
getCatalogByIdWhereSizeAndFrom(0, 20)
Because "with" sounds like a JOIN or mixin, while "where" stands for filtering rules.
Nice one Pate, I like Where
:+1: ok
Currently I have a resource
v1/catalog
and the generated methods are like
getCatalogAndSizeAndFrom
This name sounds no very comprehensive.
And Option would be getCatalogBYSizeAndFromAnd.... but this could be no convenient for resources like v1/catalogById/${id}
because it would generate getCatalogByIdBySizeAndFrom :S This sounds not very cool
So a better option would be using WITH first
For example CatalogByIdWithFromAndSize(0,20)