Open MarcAntoine-Arnaud opened 1 month ago
labra
commented
1 day ago Indeed, something I am currently not sure about is what is the rudof crate at all because the latest version has been published 2 months ago but we are currently not publishing a single rudof crate but more fine-grained crates like rudof-cli or shacl_ast which are more up-to-date.
Which are the links that are broken?
MarcAntoine-Arnaud
commented
1 day ago Ho yeah, I have opened this issue just after you changed the name. So it's mostly here: https://crates.io/crates/rudof
But as it's a not used crate, I suggest:
labra
commented
16 hours ago I think that having an façade rudof crate with a functionality similar to that of the rudof_cli but intended to be used programmatically would make sense
In that way, we could encourage the Rust users to use the methods from that crate trying to define a more stable API on that module.
I am hesitating about the name of the crate, we could call it rudof, but maybe I will call it rudof_lib by now, reserving rudof, and mainly because in that way, the structure of the project I think is cleaner, as we will have a folder for each crate.
MarcAntoine-Arnaud
commented
8 hours ago For me it can be rudof the main crate.
A crate can be a lib and may includes also a bin folder with some executables (as mentioned here https://doc.rust-lang.org/cargo/reference/cargo-targets.html#binaries).
It means you have only one crate that reference the cli and the lib.
labra
commented
5 hours ago Yes, indeed, I think we could do it. I tried to keep rudof_cli and rudof_lib separated to avoid conflicts, but maybe we should consider grouping them back together.
We will do it once we are sure how to do it properly. I created issue #200 to do it (which by the way is a nice issue number)
on crates.io some links are broken: https://crates.io/crates/rudof