<h3 dir="auto">What problem does this feature solve?</h3>
<p dir="auto">you know sometimes you cant always use variable form filter when you want to Extract the abstract logic on filter<br>
such like:<br>
.item1<br>
.item-count {{(item.shouldFilterValue[0] || 0) | item.filterName[0]}}<br>
.item2<br>
.item-count {{item.shouldFilterValue[1] || 0 | item.filterName[1]}}<br>
.item3<br>
.item-count {{item.shouldFilterValue[2] || 0 | item.filterName[2]}}<br>
the code above is served as a basic child component,and its parent component will provide string form filter name like:<br>
const normalRunItem = {<br>
title: ['Km', 'Speed', 'Time'],<br>
shouldFilterValue: [distance, pace, secondDuration],<br>
filterName: ['calRunningDistance', 'formatRunPace']<br>
}<br>
const cyclingItem = {<br>
title: ['Km', 'Km/h', 'Time'],<br>
shouldFilterValue: [distance, [secondDuration, distance], secondDuration],<br>
filterName: ['calCyclingDistance', 'calAverageSpeed']<br>
}<br>
const hikingItem = {<br>
title: ['Km', 'Pace', 'Duration'],<br>
shouldFilterValue: [distance, steps, secondDuration],<br>
filterName: ['calCyclingDistance', '']<br>
}</p>
<h3 dir="auto">What does the proposed API look like?</h3>
<p dir="auto">support string form filter gonna be ok</p>
<p dir="auto">According to the document, the filterId would be parsed by using the text after | as the filterId. Is there possible to support use expression as the filterId. For example: we can use obj.filter as the filterId. vue can calc the expression, then use the result to be the filterId? Thx for your time:)</p>