-
Notifications
You must be signed in to change notification settings - Fork 205
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
Relabel "Experimental" to "Early Access" and reorganise pages #5411
Conversation
a5ce094
to
3beaf33
Compare
app-dev/bindings-ts/index | ||
app-dev/bindings-java/index |
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.
What is happening to those? You seem to have removed them from the index but it looks like you didn’t believe the files.
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.
Ah I missed that we have a separate index for the ledger API, thanks for the explanation!
Moved them below the "The Ledger API" item. I tried to bundle everything
related to direct interaction with the Ledger API there.
…On Fri, 3 Apr 2020, 12:01 Moritz Kiefer, ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In docs/source/index.rst
<#5411 (comment)>:
> app-dev/bindings-ts/index
- app-dev/bindings-java/index
What is happening to those? You seem to have removed them from the index
but it looks like you didn’t believe the files.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5411 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJW7WQUMCBZKEH2CR3UC6STRKWXVXANCNFSM4L3X6ASA>
.
--
This message, and any attachments, is for the intended recipient(s) only,
may contain information that is privileged, confidential and/or proprietary
and subject to important terms and conditions available at
http://www.digitalasset.com/emaildisclaimer.html
<http://www.digitalasset.com/emaildisclaimer.html>. If you are not the
intended recipient, please delete this message.
|
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.
LGTM, thanks!
CHANGELOG_BEGIN - Move daml2ts, bindings-ts and JSON API out of experimental section in docs - Rename Experimental to Early Access in docs and assistant - Reorganise the docs a little bit to de-emphasise the Ledger API CHANGELOG_END
3beaf33
to
444a810
Compare
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.
Awesome. Thanks a lot!
You can move the files around if you want to. Moving files and reshuffling the index are completely orthogonal. Since I took your suggestion of moving the quickstart under the java bindings, I don't think there's a real conflict here, probably a merge conflict, though. |
- pointed out by @cocreature; thanks
* move JSON API doc to "Building applications" * stop describing JSON API as experimental; limit to calling WebSocket endpoints alpha * remove "(experimental)" from daml json-api docstring * add changelog CHANGELOG_BEGIN - [JSON API] First stable version of the ``/v1`` endpoints, with the exception of the WebSocket endpoints, which remain in alpha. See `issue #4458 <https://github.com/digital-asset/daml/issues/4458>`_. CHANGELOG_END * move json-api in PDF ToC, adapting to #5411 c496e2b - pointed out by @cocreature; thanks
This resolves #5407 and #5408. It's likely to lead to conflicts with some other changes by @S11001001 and @rohanjr, but I thought I'd present my complete suggestion for the tidyup.
CHANGELOG_BEGIN
daml2ts
,bindings-ts
and JSON API out of experimental section in docsCHANGELOG_END
Pull Request Checklist
CHANGELOG_BEGIN
andCHANGELOG_END
tagsNOTE: CI is not automatically run on non-members pull-requests for security
reasons. The reviewer will have to comment with
/AzurePipelines run
totrigger the build.