You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
but not per crate. It would be nice to be able to say "ignore links to String, but only in the core crate".
I'm not sure how to fit that in to the existing syntax - I think we might have hemmed ourselves in by getting too clever with the keys. Maybe something like this?
[[crate]]
name = "core""String" = "../../std/str/struct.String.html"
That means you can't ignore a name link I think, but I'm not sure what other syntax intra-conv could use.
The text was updated successfully, but these errors were encountered:
I agree this would be nice to have but I'm not sure how to fix it. Your proposed syntax is nice but I don't want to lock people out of using name or any other identifier within a crate-wide ignore.
The current solution is to have an ignore file per-crate but this obviously does not scale well.
I'll think about it some more before making a choice.
The current solution is to have an ignore file per-crate but this obviously does not scale well.
Oh I didn't think of that - that would probably work for me. I'm not sure how intraconv detects crates though, I think if I run it in the root of a workspace it will use the same ignore file for each?
Yes, you would have to run it for each crate separately and either give it a specific ignore file or put one in each crate directory and run intraconv from this directory. Not very agreeable to use but it should work
Right now you can ignore links globally:
and per-file:
but not per crate. It would be nice to be able to say "ignore links to
String
, but only in thecore
crate".I'm not sure how to fit that in to the existing syntax - I think we might have hemmed ourselves in by getting too clever with the keys. Maybe something like this?
That means you can't ignore a
name
link I think, but I'm not sure what other syntax intra-conv could use.The text was updated successfully, but these errors were encountered: