The component needs a fixed property to carry business data

[betgar]

• I have searched the issues of this repository and believe that this is not a duplicate.

What problem does this feature solve?

The component needs a fixed property to carry business data, and the fixed attribute can prevent potential conflicts with the component's own properties.

What does the proposed API look like?

// example: Select Options
// Options:  array<{value, label, [disabled, key, title]}>
// add a `extraData` prop for business data
// demo
const options = [
{
key: 1,
value: 1,
title: 'Org',
extraData: {
// some props
}
}
]

[sendya]

try

<a-select>
  <a-select-option v-for="item in businessData " :value="item.value">{{ item.xxx }}</a-select-option>
</a-select>

[sendya]

or

<a-select :options="businessData.map(item=>return { label:item.xxx, value: item.abc })" />

[betgar]

@sendya First, thank you for you work and thank you team.
You misunderstand what I say. Because the select options.value only be string | number, that's cannot satisfy the need.
When I use select change event, I need the second arguments options, onChange(value, option), but option is not a pure data model, it is a VNode, so I debug it.

Because the in the onChange handler I need the value and other data , so I give the option data model like this

const options = [
  {
      value: 6626079,
      title: 'Test org'
      orgCode: 'test',
      orgId: 6626079
  }
]

<a-select :options="options" @change="onChange"/>
but when I get it inside the onChange handler, I must be write it like this option.data.props.orgCode. This code has big risk in the future.

A other example: The tree onCheck event , the handler signature is function(checkedKeys, e:{checked: bool, checkedNodes, node, event}), the e.node is also a VNode type, so when I want get tree node prop isLeaf, I do it like this.

I don't know is there have other ways to do this. If no, the code has big risk in future. So I hope team, consider that, give a fixed property or fixed method to carry other data which I passed to the Component options. So if possable, I hope team consider
my advice.

example:

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.