feat: include nodePath as argument to template functions in TreeView nodes

[joaoassisb]

No description provided.

[assisrafael]

@joaoassisb after analysing this PR I decided to revert your previous commit. I think you should work more in the proposal and describe what use cases this feature will enable.

[joaoassisb]

@joaoassisb after analysing this PR I decided to revert your previous commit. I think you should work more in the proposal and describe what use cases this feature will enable.

@assisrafael the use case is to simplify the usage of TreeViews with Forms. At the moment, the template function passes only the item,index and parentItem, making a lot harder to handle paths and possible changes.

I updated the TreeViewExample to illustrate better my use case.

Now I can use a FormInput using the relativePath in the name of the input, and the changes will automatically updates the initial nodes structure.

[assisrafael]

@assisrafael the use case is to simplify the usage of TreeViews with Forms. At the moment, the template function passes only the item,index and parentItem, making a lot harder to handle paths and possible changes.

Your use case make sense.
Regarding the PR content, I think it would be better with the prop would be called nodePath instead of relativePath.

[assisrafael]

Instead of using a ternary here you could set "" as the default value for the prop