Figure out name

[epage]

Looks like the cargo-api name is being squatted on, see https://crates.io/crates/cargo-api

[epage]

I've emailed foresterre. We'll see where that goes.

So far, the only other name i thought of is to expand it to cargo crate-api.

[Enselic]

I completely independently started working on a project with seemingly the same goal, found at https://github.com/Enselic/public_items.

I was actually thinking about using the crate name cargo-public-items, but have not done so yet.

Maybe that would be a good name for this project? You seem to be way ahead of me so I currently don't plan on developing my project further. Seems like a better idea to join forces, and in that case your project is a better base.

[epage]

Would love to collaborate! Also hoping to hear back soon from the cargo-breaking maintainers about collaborating there as well (this started as a PoC for a rustdoc implementation of cargo-breaking).

Something feels off about calling whats implemented cargo public-items though I can say precisely why. I feel like it needs to be making a more direct reference to an API, to semver, or something related to those.

[scrabsha]

Would love to collaborate! Also hoping to hear back soon from the cargo-breaking maintainers about collaborating there as well (this started as a PoC for a rustdoc implementation of cargo-breaking).

Hello! I think this comment is relevant.

(additionally, we have a reserved crate name on crates.io 🙂)

[epage]

👋

When I was using cargo-breaking, something I felt would help me debug things / understand what it is taking into account is the ability to dump the API. This led me to starting more generic, being unsure how different ideas would be exposed (dumping the API, diffing the api, generating a changelog, suggesting a next version, etc. At the moment, diffing, changelogs are handled through --format and in #14 I was considering version suggestions being the same. So it might work out to be under a more specific name like cargo breaking.

Thoughts?