Skip to content

Commit 0c0a2a2

Browse files
committed
chore(docs): mention data sources for feature and module tables
1 parent 6c82001 commit 0c0a2a2

2 files changed

Lines changed: 7 additions & 2 deletions

File tree

docs/roadmap/features.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@
66
> [!NOTE]
77
> Detailed information about each feature will be added soon.
88
9+
Contribute to this data here: [features.json](https://github.com/Kitware/vtk-wasm/blob/main/docs/roadmap/features.json)
10+
911
<script setup>
1012
import roadMapData from './features.json';
1113
</script>

docs/roadmap/modules.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,10 @@
11
# Module Availability
22

3-
This table categorizes VTK modules based on their availability in the JavaScript API, indicating whether they are automatically marshaled, manually marshaled, or ignored for some reason.
3+
This table categorizes VTK modules based on their availability in the JavaScript API, indicating whether the classes are marshalled, or ignored for some reason.
44

5-
Use search and status filters to quickly find module availability.
5+
The data is sourced from the VTK GitHub repository, where the status of each module is tracked in three categories: [auto-marshalled](https://github.com/Kitware/VTK/blob/master/Utilities/Marshalling/VTK_MARSHALAUTO.txt), [ignored](https://github.com/Kitware/VTK/blob/master/Utilities/Marshalling/ignore.txt), and [manually marshalled](https://github.com/Kitware/VTK/blob/master/Utilities/Marshalling/VTK_MARSHALMANUAL.txt).
6+
7+
> [!TIP]
8+
> Use search and status filters to quickly find module availability.
69
710
<ModulesCoverageTable />

0 commit comments

Comments
 (0)