Skip to content

Rust: add docs for rust#10

Merged
tasn merged 2 commits into
etesync:masterfrom
geovie:add-rust-docs
Dec 5, 2020
Merged

Rust: add docs for rust#10
tasn merged 2 commits into
etesync:masterfrom
geovie:add-rust-docs

Conversation

@geovie

@geovie geovie commented Dec 2, 2020

Copy link
Copy Markdown
Contributor

WIP PR so that everyone knows I'm working on this 😊 will finish it the next few days

Ready: closes etesync/etebase-rs#12

@geovie geovie marked this pull request as draft December 2, 2020 20:31
@tasn

tasn commented Dec 3, 2020

Copy link
Copy Markdown
Member

😍 😍 😍
Looking forward to this, thanks a lot!

@geovie geovie marked this pull request as ready for review December 4, 2020 21:20
@geovie

geovie commented Dec 4, 2020

Copy link
Copy Markdown
Contributor Author

@tasn This should be ready for review now

@tasn tasn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a quick look and everything looks great. I haven't tested it locally yet, though I assume it compiles and renders correctly (I'll do it before merging).
I only have one tiny comment that I'm happy to fix myself, and one question:
Should we wait until etesync/etebase-rs#13 is merged (and this adjusted accordingly), or would you rather have it in two steps?

Thanks a lot! I'm so happy to have this!

Comment thread docs/installation.md Outdated

```toml
[dependencies]
etebase="..."

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you maybe add a comment that people should set the version and show an example? I know that Rust people will most likely already know that, but I think it will be more "noob-proof". What do you think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I didn't want to add a version as it's likely to get out of date soon.
Adding it as comment should be fine and we could also add the crates.io badge crates.io to the description before the code block

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a really good idea! After we merge this I'll do it for all the rest of the libraries!

Maybe say something like use the version from above (needs better wording), for example: "^0.4.1" so people know to use ^? I'd rather they don't pin too harshly so that they get bugfixes.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@geovie

geovie commented Dec 5, 2020

Copy link
Copy Markdown
Contributor Author

I'd merge this as is now (with the change you requested) and adjust it later, as I have some more input regarding the rust api based on the docs.

Should I open an issue with my proposals in the https://github.com/etesync/etebase-rs repository or should I comment in this PR here in the codeblocks where I think the api could be improved for the user?

@tasn

tasn commented Dec 5, 2020

Copy link
Copy Markdown
Member

OK, so I'll wait for your change and merge it.

Comments on the Rust API: open an issue in that repo, that would be better. Thanks!

@tasn tasn merged commit bf87b99 into etesync:master Dec 5, 2020
@tasn

tasn commented Dec 5, 2020

Copy link
Copy Markdown
Member

Great, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add usage guides to docs.etebase.com

2 participants