@kflansburg is there a specific reason

@kflansburg is there a specific reason you removed this re-export in PR 481?
pub use crate::schedule::*;
pub use crate::schedule::*;
11 Replies
avsaase
avsaase7mo ago
It breaks usage of ScheduledEvent
Unknown User
Unknown User7mo ago
Message Not Public
Sign In & Join Server To View
avsaase
avsaase7mo ago
No worries. It happens. Mistakes like this could be caught by tools like cargo-semver-checks. They provide github actions to automate these checks.
Unknown User
Unknown User7mo ago
Message Not Public
Sign In & Join Server To View
avsaase
avsaase7mo ago
Yes that's true but in this case the tool would have made it clear that some previously accessible types where not accessible anymore. I haven't checked yet what the exact CI setup should be to make this work.
Unknown User
Unknown User7mo ago
Message Not Public
Sign In & Join Server To View
avsaase
avsaase7mo ago
What I would try to do is build and ideally run the examples in CI
Unknown User
Unknown User7mo ago
Message Not Public
Sign In & Join Server To View
avsaase
avsaase7mo ago
Looks like the pr checks don't run on the release PR
Unknown User
Unknown User7mo ago
Message Not Public
Sign In & Join Server To View
Want results from more Discord servers?
Add your server