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
The bl-table component currently expects the selected prop to always be of type string, even when the actual data IDs are numbers. This creates an inconsistency between the data structure and the expected prop type. The component should be updated to accept both strings and numbers for the selected prop to ensure compatibility and flexibility with various datasets.
There's a workaround for this bug in Vue like this:
/* BUG: This computed property is needed because of a Baklava table bugwhere the component expects selected IDs to always be strings,even when the actual data IDs might be numbers */constselectedIdsAsStrings=computed(()=>{if(!props.selected)return[]returnprops.selected.map((id)=>String(id))})
Media & Screenshots
Screen.Recording.2024-11-27.at.3.11.14.PM.mov
Baklava Version
3.2.0 (stable)
Operating system
macOS: 15.1.1 (24B91)
Microsoft Edge: Version 131.0.2903.51 (Official build) (arm64)
Priority this issue should have
Medium (should be fixed soon)
Please review the checkboxes that are applicable.
This issue is directly related to React
The text was updated successfully, but these errors were encountered:
Issue description
The bl-table component currently expects the selected prop to always be of type string, even when the actual data IDs are numbers. This creates an inconsistency between the data structure and the expected prop type. The component should be updated to accept both strings and numbers for the selected prop to ensure compatibility and flexibility with various datasets.
There's a workaround for this bug in Vue like this:
Media & Screenshots
Screen.Recording.2024-11-27.at.3.11.14.PM.mov
Baklava Version
3.2.0 (stable)
Operating system
macOS: 15.1.1 (24B91)
Microsoft Edge: Version 131.0.2903.51 (Official build) (arm64)
Priority this issue should have
Medium (should be fixed soon)
Please review the checkboxes that are applicable.
The text was updated successfully, but these errors were encountered: