Mirrors/bevy
2
0
Fork 0
mirror of https://github.com/bevyengine/bevy synced 2024-12-22 19:13:08 +00:00
Code Issues Projects Releases Packages Wiki Activity
bevy/crates/bevy_ecs_compile_fail_tests/Cargo.toml

14 lines
391 B
TOML
Raw Normal View History

Assert compiler errors for compile_fail tests (#3067) # Objective bevy_ecs has several compile_fail tests that assert lifetime safety. In the past, these tests have been green for the wrong reasons (see e.g. #2984). This PR makes sure, that they will fail if the compiler error changes. ## Solution Use [trybuild](https://crates.io/crates/trybuild) to assert the compiler errors. The UI tests are in a separate crate that is not part of the Bevy workspace. This is to ensure that they do not break Bevy's crater builds. The tests get executed by the CI workflow on the stable toolchain.
2021-11-13 22:43:19 +00:00
[package]
name = "bevy_ecs_compile_fail_tests"
Bump Bevy to 0.7.0-dev (#4230) # Objective - The [dev docs](https://dev-docs.bevyengine.org/bevy/index.html#) show version 0.6.0, which is actively misleading. [Image of the problem](https://cdn.discordapp.com/attachments/695741366520512563/953513612943704114/Screenshot_20220316-154100_Firefox-01.jpeg) Noticed by @ickk, fix proposed by @mockersf. ## Solution - Bump the version across all Bevy crates to 0.7.0 dev. - Set a reminder in the Release Checklist to remember to do this each release.
2022-03-19 03:54:15 +00:00
version = "0.7.0-dev"
Assert compiler errors for compile_fail tests (#3067) # Objective bevy_ecs has several compile_fail tests that assert lifetime safety. In the past, these tests have been green for the wrong reasons (see e.g. #2984). This PR makes sure, that they will fail if the compiler error changes. ## Solution Use [trybuild](https://crates.io/crates/trybuild) to assert the compiler errors. The UI tests are in a separate crate that is not part of the Bevy workspace. This is to ensure that they do not break Bevy's crater builds. The tests get executed by the CI workflow on the stable toolchain.
2021-11-13 22:43:19 +00:00
edition = "2021"
description = "Compile fail tests for Bevy Engine's entity component system"
homepage = "https://bevyengine.org"
repository = "https://github.com/bevyengine/bevy"
license = "MIT OR Apache-2.0"
publish = false
[dev-dependencies]
Bump Bevy to 0.7.0-dev (#4230) # Objective - The [dev docs](https://dev-docs.bevyengine.org/bevy/index.html#) show version 0.6.0, which is actively misleading. [Image of the problem](https://cdn.discordapp.com/attachments/695741366520512563/953513612943704114/Screenshot_20220316-154100_Firefox-01.jpeg) Noticed by @ickk, fix proposed by @mockersf. ## Solution - Bump the version across all Bevy crates to 0.7.0 dev. - Set a reminder in the Release Checklist to remember to do this each release.
2022-03-19 03:54:15 +00:00
bevy_ecs = { path = "../bevy_ecs", version = "0.7.0-dev" }
Assert compiler errors for compile_fail tests (#3067) # Objective bevy_ecs has several compile_fail tests that assert lifetime safety. In the past, these tests have been green for the wrong reasons (see e.g. #2984). This PR makes sure, that they will fail if the compiler error changes. ## Solution Use [trybuild](https://crates.io/crates/trybuild) to assert the compiler errors. The UI tests are in a separate crate that is not part of the Bevy workspace. This is to ensure that they do not break Bevy's crater builds. The tests get executed by the CI workflow on the stable toolchain.
2021-11-13 22:43:19 +00:00
trybuild = "1.0"
Reference in a new issue Copy permalink