Closed fchabouis closed 1 year ago
Clippy is not happy, but I don't undersand what I have changed to upset it for the moment. I could correct what it is complaining about, but why is it complaining now?
I have not checked, but I think it's due to clippy updates :stuck_out_tongue_winking_eye:
I can lend you a hand if they are difficult to change
I was lost, because I thought there would be a cargo.lock
file to avoid automatic updates like that. But I read this and it makes sense.
hum, but here it's just the clippy version in CI that is not pinned isn't it? And even if it's a bit painful, I think it's nice to benefit from all the upgrades
I have applied the Clippy's suggestions
...and pathways.txt
linked to https://github.com/etalab/transport-site/issues/2958
I was wondering if I was misusing the Error, just passing the filename with the stop_id like that?
But the error is used in other context, where the filename is not necessarily known, so maybe it is fine. Let me know :)
Thanks!