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
{{ message }}
This repository has been archived by the owner on Apr 1, 2022. It is now read-only.
If I want to create a dynamic component for selecting data at the cell level, it's necessary for me to tell the dynamic component what the select options are as well as the currently selected value. At the moment, the only way I can do this is to (very hackily) use the row property. Possibly, a better way to do this would be to add an extra "options" property when tdComp dynamic components are instantiated - note, that this options property would be something that could be defined at the column level so that it is no longer necessary to have to specify the select options per row.
N.B - I'm using 'options' here as a non component specific container for extra data that could be used with any dynamic component. Other examples of usage could be disabling a dynamic component for an entire column - in this case the column date would be col.options.disabled = true.
BTW - such a shame that this datatable component is deprecated. More than anything, I'm adding this issue here so that I can make my change and then file a pull request. Then if anyone else needs the same kind of functionality they can take a look at my code.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
If I want to create a dynamic component for selecting data at the cell level, it's necessary for me to tell the dynamic component what the select options are as well as the currently selected value. At the moment, the only way I can do this is to (very hackily) use the row property. Possibly, a better way to do this would be to add an extra "options" property when tdComp dynamic components are instantiated - note, that this options property would be something that could be defined at the column level so that it is no longer necessary to have to specify the select options per row.
N.B - I'm using 'options' here as a non component specific container for extra data that could be used with any dynamic component. Other examples of usage could be disabling a dynamic component for an entire column - in this case the column date would be col.options.disabled = true.
BTW - such a shame that this datatable component is deprecated. More than anything, I'm adding this issue here so that I can make my change and then file a pull request. Then if anyone else needs the same kind of functionality they can take a look at my code.
The text was updated successfully, but these errors were encountered: