-
Notifications
You must be signed in to change notification settings - Fork 131
Documentation for proc macros not rendered correctly #904
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
Comments
I'm not sure either. Perhaps the behavior of The reason why the "proper" documentation for those macros is in We should check if there is a way to put the docstrings into |
I tried to get the right documentation to render in Do we need those examples to compile? We have other tests for those macros, so imo the easiest solution is to move the docs to scylla_macros crate and mark examples as
Note the last sentence, that should not be there. |
It's not about testing the implementation, it's about making sure that examples in the documentation are up-to-date. I'd rather avoid marking them as "ignore" so that we don't accidentally suggest incorrect code to the users. How do other projects handle this issue? Tokio, for example - they have the I now remember that I investigated this long ago actually. I wrote a proposal for In our case, |
Adding dev-dependency on scylla in scylla-macros allows doc tests to compile. However, it creates another problem :( Documentation for serialization macros refers to items from scylla_cql - and I don't see a good way to do this, even if scylla_cql is a dev-dependency. One option is to use absolute links to docs.rs - it is a problem for very obvious reasons. That could maybe be a good tradeoff, but I don't think we could get the links working both in |
No, I don't. However, users should look at the docs in the |
Documentation for
SerializeCql
andSerializeRow
is not rendered properly.https://docs.rs/scylla/latest/scylla/derive.SerializeCql.html
https://docs.rs/scylla/latest/scylla/derive.SerializeCql.html
Both docs say
See the documentation for this item in the scylla crate.
- which we are obviously looking at.I'm not sure why that happens.
scylla
re-exports those items fromscylla-cql
crate, which re-exports them fromscylla-macros
and documents them.Documentation for
scylla-cql
renders correctly, so I don't get whyscylla
uses docstrings directly fromscylla-macros
. @piodul any ideas?The text was updated successfully, but these errors were encountered: