Parker McMullin

I can second this. Mine is more of a 30/70 split though, so I can't see much of my actual code.

@phlexib Sounds great! I think it depends on when you'd like it merged and usable. Since it may be a couple weeks until the v1 migration is complete, perhaps you'd...

@phlexib Last night I tagged the release of `v4.0.0`, so you can add this to the updated master branch.

Thank you, bot! 😂

I'm investigating a solution in https://github.com/parker-codes/todo_by/pull/5. Ideally we could show an error/warning in the editor and only log out warnings for the current project. Since diagnostics are not on stable...

Just merged the PR to not fail builds. It still fails tests though, so I'll be looking for a solution to that.

Lib authors could perhaps have an optional envar like `TODO_BY_LIB=true` that would not get included in the crate repo (via git dep) or crates.io assets. Perhaps there's a Cargo metadata...

[Someone on Reddit](https://www.reddit.com/r/rust/comments/13gujgg/comment/jk27loc/?utm_source=share&utm_medium=web2x&context=3) brought up the CARGO_PRIMARY_PACKAGE envar. Here's what it says in [the docs](https://doc.rust-lang.org/cargo/reference/environment-variables.html): > **CARGO_PRIMARY_PACKAGE** — This environment variable will be set if the package being built is...

I tested the CARGO_PRIMARY_PACKAGE envar and it's a dead end. I created a dependency tree to test like todo_by library_using_todo_by binary_using_library ~~The envar was not present in any of these...

Yep, this is what I used. I logged out the value along with the project name so I would know which depth the value came from. All said the same...