-
Notifications
You must be signed in to change notification settings - Fork 51
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
Exposing diplomat-tool
through a library
#348
Conversation
I'd rather not commit to an API here just yet; especially since a thing I definitely want to do is give backends the ability to accept parameters. |
It's pre-1.0 so personally I don't have a huge concern with making a starter API |
|
||
pub fn gen( | ||
entry: &Path, | ||
target_language: &str, |
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.
at the very least I think we should have a config struct or something that encapsulates all this
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.
we should also perhaps have a CLI feature
Hm, fair. I do think we should spend some effort cleaning up the API though |
There's a lot to clean up in Diplomat. One thing I noticed is that the language gets passed around everywhere as a |
Clients like ICU4X need to version
diplomat-tool
along with the other diplomat crates. Cargo cannot at the moment version binaries, exposing a library is the recommended workaround (rust-lang/cargo#2267).