H
Håvard Danielsen
Guest
A fluent query builder sounds very interesting, but there should be a query model(wrapper) class that takes the entire json info as a parameter to a method or the constructor. If the query model is structured according to the query syntax then it would not be internal and the interface and its consumers would not need to change if the internal json stucture changes. One would only need to change the implementation of the JSON parsing. I have implemented batching, filtering and sorting for other JavaScript frameworks and they have the exact same information as the KendoUI, and could thus all use the same interface, there would just be different parser implementations. Personally, I would implement an interface that has all request info, including paging and sorting that can be passed to Business Entities or any data access. It may extend the query model or it may just use the query model under the covers. The fluent builder should ideally work against the same model/class.
Continue reading...
Continue reading...