Comments (5)
Ok, I decided for a breaking change and stop to support the #[macro_use]
. Now I used the same approach used by macro-vis
and hide the original macro by a random name.
Export at the root now works and I avoided to introduce a new wired syntax like #[no_local]
. You can also export a template from a sub module but you should point it with the full path or reexport it at the root.
from rstest.
Playing with macros is tricky and I cannot recognize that the template is in a module or not in the procedural macro so I cannot change the behavior of #[export]
annotation to fit this possibility. The only way to implement this behavior that I can see is to introduce a #[no_local]
annotation that can be used to remove pub(crate) use #macro_name as #macro_name;
trick used to have locally templates.
from rstest.
I see, that's a tricky situation. There are workarounds floating around like macro-vis
and macro-pub
which are based on name mangling. There are some caveats listed but overall looks like an improvement (both to avoid this particular issue and to allow the generated test case to be exported from the module namespace)
from rstest.
I hope to publish the new version for the end of the week....
from rstest.
Done 🎆
from rstest.
Related Issues (20)
- skip cases based on feature flag? HOT 5
- `#[once]` fixtures are unsound for types that are not `Sync` HOT 4
- clippy::duplicated_attributes warning with rust 1.79.0-nightly HOT 3
- By-reference fixtures HOT 12
- Update `rstest_reuse` docs and release new version
- `#[from(source)]` should accept path also and not just idents
- rstest_reuse: "the `async` keyword is missing from the function declaration" HOT 1
- replace return <expr>; with <expr> [needless_return] HOT 3
- Support dynamic `#[values]` HOT 1
- Feature: Optional label in the `#[case...]` HOT 1
- Dynamically set #[values(..)] HOT 1
- New test files are only recognized after `cargo clean` HOT 4
- feat: provide a cargo feature to disable the proc macro inference in #221 HOT 2
- consider adding a `wasm-bindgen` feature HOT 1
- Recommendation on choosing between different sets of `#[values(...)]`?
- Mixing `#[rstest]` and `#[serial]` breaks VS Code's IntelliSense with rust-analyzer HOT 3
- Possibility of resolving a fixture only once per test?
- Automatically test all variants of an enum HOT 1
- unused warning for case variables used by fixture #[with(var)] HOT 1
- Can #[files] use relative paths HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rstest.