We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the filtered value is treated as $item[$field]. I'm not really frontend developer, but I think yii2 knew it too: https://github.com/yiisoft/yii2/blob/f8611d170d77f8b89f24bd80e7f3b6b2a8947380/framework/grid/DataColumn.php#L232
$item[$field]
Yii3 also uses <field>.<subfield> with ArrayHelper::getValue()
<field>.<subfield>
ArrayHelper::getValue()
Currently not supported.
in #28 issue also affect the implementation.
The text was updated successfully, but these errors were encountered:
I think there's no need to support that on data provider level. Having it at grid level should be enough.
Sorry, something went wrong.
An interesting question, because basically you can avoid (eg. flatten, filter in browser with javascript). But I can imagine its use:
$data = StoreAR::find()->with('location')->where(..public..)->asArray()->all(); // eg counts less than 100 $cache->set('stores', $data); // ... $data = $cache->get('stores'); $reader = (new IterableDataReader($data)) ->withFilters(new Like('location.city', $cityFilter)); // ...
I'd postpone it till grids are implemented.
No branches or pull requests
What steps will reproduce the problem?
Currently, the filtered value is treated as
$item[$field]
. I'm not really frontend developer, but I think yii2 knew it too:https://github.com/yiisoft/yii2/blob/f8611d170d77f8b89f24bd80e7f3b6b2a8947380/framework/grid/DataColumn.php#L232
What is the expected result?
Yii3 also uses
<field>.<subfield>
withArrayHelper::getValue()
What do you get instead?
Currently not supported.
Additional info
in #28 issue also affect the implementation.
The text was updated successfully, but these errors were encountered: