Hello, I've found a place in one of my apps where I have a bug which is related to a change in behaviour which occurred actually quite some time ago, precisely:
old behaviour: SmartClient Version: v13.0p_2022-09-09/Enterprise Development Only (built 2022-09-09)
new behaviour: SmartClient Version: v13.0p_2022-09-12/Enterprise Development Only (built 2022-09-12)
it can be reproduced in the expansionLimitedWithDetails sample, with this test case:
in practice there's an implicitCriteria regarding a field which doesn't appears in the response data.
With the old behaviour, when you type Exe in the category field, it will filter and show the only matching record.
With the new behaviour, no record is shown.
As I'm a bit worried to have other similar cases, and it's not easy for me to discover them, I want to ask:
- could you please confirm that the new behaviour is the "right" behaviour and won't change?
- do you think it's possible to detect similar situations (in the framework or even in my app code) to log a warning?
old behaviour: SmartClient Version: v13.0p_2022-09-09/Enterprise Development Only (built 2022-09-09)
new behaviour: SmartClient Version: v13.0p_2022-09-12/Enterprise Development Only (built 2022-09-12)
it can be reproduced in the expansionLimitedWithDetails sample, with this test case:
Code:
isc.ListGrid.create({ ID: "itemList", width:500, height:300, showFilterEditor:true, // use the supplyItemWithOps dataSource and use it's "outputsLimitedFetch" operation. // this demonstrates using "outputs" on an operationBinding to forcibly limit the data // retrieved for each row dataSource: supplyItemWithOps, fetchOperation: "outputsLimitedFetch", autoFetchData: true, //fetchMode:"local", fields: [ {name: "itemName"}, {name: "SKU"}, {name: "category"} ], implicitCriteria:{units:"Roll"} });
With the old behaviour, when you type Exe in the category field, it will filter and show the only matching record.
With the new behaviour, no record is shown.
As I'm a bit worried to have other similar cases, and it's not easy for me to discover them, I want to ask:
- could you please confirm that the new behaviour is the "right" behaviour and won't change?
- do you think it's possible to detect similar situations (in the framework or even in my app code) to log a warning?
Comment