-
Notifications
You must be signed in to change notification settings - Fork 111
Update current
#322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update current
#322
Conversation
* add world file parsing * add world file parsing * clarity and cleanup * read world from reader * add option to preload maps in world * fix documentation, revert auto load maps * remove tmx map variable from worldmap * Remove automatic dir pattern testing * formatting and better docs * formatting and better docs * Moved pattern utils to World impl * Missed dep for world feature and cargo build step * match_path and match_paths * add match_path to WorldPattern * reduce utf-8 checks on path iteration * match_path_impl and readme update * empty vecs instead of option * empty vecs instead of option * Oddities with readme * fix load_world docs * fix source not populating
bjorn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for making the 0.14 release!
|
What's up with this, btw? |
|
No clue. Maybe a new Rust version changed the |
|
Seems it's this: https://doc.rust-lang.org/edition-guide/rust-2024/rustdoc-nested-includes.html |
|
Weird. The logs for build (push) which doesn't fail treats the doctests as being in the README: I'm not exactly sure what the difference between both builds is. Any ideas @bjorn? |
|
Sorry for bothering you again, but do you have an ETA for the actual release ? |
|
Sorry, which release? If you are referring to the one that includes #320, I uploaded that one 3 weeks ago to crates.io: https://github.com/mapeditor/rs-tiled/releases/tag/v0.14.0 https://docs.rs/tiled/0.14.0/tiled/ This PR is just to update the current branch, but there are a few errors with the CI that we don't know how to fix. It isn't urgent so I haven't looked further into it. |
|
Oh my bad, I saw this PR and though #320 was not yet published. |


Remember to do merge from Git