Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move integration crates in their own workspaces #69

Merged
merged 1 commit into from
Jul 13, 2024

Commits on Jul 12, 2024

  1. Move integration crates in their own workspaces

    Everytime you hit ctrl+s in VS code, the whole project in checked, which
    normally is a nice thing, and I would not like to disable that in my
    configuration.
    
    But in rinja, the diffent integration crates don't work well with one
    another and every single one will have compile errors in the automatic
    check, because `rinja_derive` won't know what the relevant `rinja_xyz`
    crate is. This renders the automatic check useless. Then it takes ages
    to compile and recompile all transitively used `proc_macros`.
    
    This PR moves all integration crates in there own, individual
    workspaces. `cargo check` will ignore them unless you traverse manually
    into their folders. The CI is set up to do just that.
    Kijewski committed Jul 12, 2024
    Configuration menu
    Copy the full SHA
    429eae1 View commit details
    Browse the repository at this point in the history