Skip to content

Feature soundness test should include the wasm32 target too #4121

@Madoshakalaka

Description

@Madoshakalaka

Our current feature soundness step is on native target only:

cargo hack clippy
-p yew -p yew-agent -p yew-router
--feature-powerset --no-dev-deps
--keep-going
-- -D warnings

It doesn't catch warnings like this one

We should run cargo hack either only on wasm32 (the major use case) or both on wasm32 and native.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-ciArea: The continuous integration

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions