Fix logos_path in generated code#348
Conversation
|
Nice! Could you add a small test that would break if your fix was not present? |
|
I've already considered it, but unfortunately I don't think it's that easy. For example:
That should make sure it does not break again, but it adds two new crates to the repository just for this. If that's okay, please tell me where to put them and I can do that. (Maybe there's something I'm missing, but I think this is the only way.) |
|
Hello @jannik4, sorry for the late reply, but I needed to think a bit about this :-) So I don't think we really need to create a new crate, depending on how cargo actually resolves dependencies. I have two ideas:
The only doubt I have is whether the tests will fail without your fix, because cargo may be smart enough to see that your re-export points to the same What do you think? |
|
Isn't this exactly the same as the already existing test |
|
Hum ok I guess this isn't as easy as I would have hoped, but not problem I will merge this like this then ;-) Thanks for your work! |
No description provided.