You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently have multiple cases where data is being directly queried from a database to be displayed in a QTree.
The field name which contains the record label is 'value' although Quasar expects 'label'. I currently have a transform function which replaces the 'value' field with a 'label' field for every record.
The ability to specify, I want to the tree for each node to display the node.value field would be great and allow me to get rid of this step!
Envisioning a label-key field much like node-key.
Looking at the code, I do see that the filter method expects a label field which would seem to require a change as it is not possible to access other props i.e. label-key inside a prop default function AFAIK
I currently have multiple cases where data is being directly queried from a database to be displayed in a QTree.
The field name which contains the record label is 'value' although Quasar expects 'label'. I currently have a transform function which replaces the 'value' field with a 'label' field for every record.
The ability to specify, I want to the tree for each node to display the node.value field would be great and allow me to get rid of this step!
Envisioning a label-key field much like node-key.
Looking at the code, I do see that the filter method expects a label field which would seem to require a change as it is not possible to access other props i.e. label-key inside a prop default function AFAIK
The text was updated successfully, but these errors were encountered: