-
Notifications
You must be signed in to change notification settings - Fork 277
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
[documentation] #3878: Add the documentation-related Iroha configurat… #3879
Conversation
Let me try to understand better what is the problem we need to solve. To clarify the context, the documentation piece is the following:
You say:
So the problem is that this snippet (and other similar ones) might get outdated, right? This doesn't make much sense for me. First of all, I have a strong confusion about versioning, releases, What should the documentation rely on??? IMO, it should rely on something single. Coming back to the original issue. IMO, there is no need to integrate documentation-related [dependencies]
iroha_client.workspace = true
# or
iroha_client = { path = "../../client" } And this doesn't make any sense for the documentation. If we want to achieve a "real-world"-like Iroha-based project configuration, we might create a real-world Iroha-based project and store it as a separate repo, e.g. [dependencies]
iroha_client = { "git" = "https://github.com/hyperledger/iroha.git", branch = "iroha2-stable" } This is how you can use Iroha at the moment, in reality. Shall we create such a project? Might be a good idea. We will have a truly working independent sample. Now we have mostly ephemeral snippets of code, integrated into the main repo with crutches. Also, I want to make another point. IMHO, things like describing a In conclusion, I think we need to very clearly identify the versioning of Iroha 2, the guarantees and boundaries. The documentation needs a single, clear, and stable target to document. |
b1f3dcb
to
6db9969
Compare
Pull Request Test Coverage Report for Build 6390060375
💛 - Coveralls |
… Iroha configurations Signed-off-by: 6r1d <[email protected]>
Original issue: #3878
We're actively using the "Code snippets" feature, and I'm trying to have more.
While doing hyperledger-iroha/iroha-2-docs#394, I want to reach some granularity.
I can either have
Cargo.toml
for the "Client setup" section of the Rust tutorial here or add it to the snippets directory in Iroha 2 documentation. It has less chance of remaining unnoticed for a long time if it belongs to the main repo, at least in my opinion.Collecting a list of doc-related configurations that depend on the release in the main repo seems OK to me, but someone may disagree.
Please comment here.