Skip to content

[Feature request] restructuring of examples #240

@BitsAndDroids

Description

@BitsAndDroids

@caemor I wanted to request your blessing before spending time on this change:

Situation

The primary selling point of this library is that it is compatible with multiple platforms. The downside is that every platform requires specific dependencies and setups. In theory, it's possible to expand the dev dependencies in the Cargo.toml. But this muddies the water at a rapid pace.
It's not easy to distinguish which dependency belongs to which example.

Suggestion

My suggestion would be to follow a similar approach to the Axum examples. The main difference is that they use a parent workspace and set up every example as a separate crate.
The advantage is that every example has a dedicated Cargo.Toml. Due to the nature of your library, this could be particularly helpful in differentiating the nuances between the various platforms.

Let me know if you agree with this approach, so I can make the necessary changes (will add esp32 examples along the way).

Thanks for your work so far!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions