[Sample App] Non-WASM supported components showing up in WASM Sample App #5
Labels
bug 🐛
Something isn't working
sample app 🖼
source generator ⚙️
Uno
Issues related to Uno Platform
WASM
Bugs related to working with WASM/Codespaces
Describe the bug
Components like
Shimmer
which use composition and aren't supported in WASM, have a Multi-target that defines as such. However, it's still appearing in the WASM sample app when generating the all solution.This is tangentially related to the local component head for WASM being copied as well when it's not supported (not sure if we have another issue for that, maybe want a separate one?).
Steps to reproduce
Expected behavior
Shimmer not shown in WASM app head.
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.
The text was updated successfully, but these errors were encountered: