* update reference doc (doc-comments in Script.daml) for daml-script/interfaces
* small english fixes
* update user doc and example for daml-script/interfaces
* build/test ScriptExample.daml at 1.15
* dont show party in interface info message
* fix for: //daml-script/export/integration-tests/golden:matches-docs-test
* disable failing integration test
Partly because the current version is from February (of this year,
fortunately), and partly because I need a more recent one to bump node
to 18 and fix the GSG for that.
Before this change, we had two error categories that were meant for the same purpose: malicious or faulty and security alert. Now, they have been merged together. As malicious or faulty was misunderstood and sometimes used instead of "SystemInternalAssumptionViolation", we've dropped that term.
Related to canton 10981
* Adding the Python bindings to the docs
Adding support for the Python bindings to the docs.
Adding a page on the Python bindings.
Adding references to them where appropriate.
* Update docs/source/app-dev/bindings-python.rst
Co-authored-by: katmurp <117752519+katmurp@users.noreply.github.com>
* Adding the phrase "(formerly known as DAZL)"
Adding the phrase "(formerly known as DAZL)" when the Python bindings are referenced for the first time on a page.
* Adding the python bindings into the TOC
Adding the python bindings into the TOC in the building applications section below Java Bindings and above Daml Script .
Co-authored-by: katmurp <117752519+katmurp@users.noreply.github.com>
* remove redundant query-store config block doc
* clean up json-api config doc
* shorter explanation of schema version
* section on query store performance
* emphasize that JSON API isn't magic
* a bit more on scaling
* small intro note about intended applications
* some thoughts on the limits of scaling
* make all the versions indirect
- suggested by @carrielaben-da; thanks
* replace JSON API with HTTP JSON API service
- suggested by @stefanobaghino-da
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* Extract Ledger API error definitions in //ledger/error-definitions
changelog_begin
SERVICE_INTERNAL_ERROR error code is created in CommonErrors and replaces the usage of LEDGER_API_INTERNAL_ERROR in ledger-api-client (as a fix).
changelog_end
* Tests in //ledger/error do not depend on //ledger/ledger-api-errors
* Remove unused dependency from //ledger/error
changelog_begin
changelog_end
* Address Martino's comment
* split JSON API production setup doc to separate documents
CHANGELOG_BEGIN
CHANGELOG_END
* remove json-api and production-setup TOCs
- properly placed in digital-asset/docs.daml.com#55
- suggested by @garyverhaegen-da; thanks
The comments refer to 0.x and can be misleading for 2.x users
(since the default is not 1.8 anymore and have not been for a
long time at this point). Furthermore, I am also relatively
sure that 1.8 is not even an option at all for 2.x users.
changelog_begin
changelog_end
Somehow our setup doesn't work with puppeteer 19+.
CHANGELOG_BEGIN
- GSG: Several TypeScript warnings have been fixed in the final "Testing
Your Web App" section of the Getting Started Guide. The
`create-daml-app` template includes an updated `config.ts` file, and the
documentation page as been updated to pin the `puppeteer` version to a
known-working one and tweak the `index.test.ts` file.
CHANGELOG_END
* Replace '1.dev only'=>'Daml-LF >= 1.15' in docs for interface functions
* Define coerceInterfaceContractId
* Test coerceInterfaceContractId in InterfaceContractDoesNotImplementInterface
* Test coerceInterfaceContractId in InterfaceConversions
* Add entry for coerceInterfaceContractId in interface reference docs
* update *.EXPECTED.desugared-daml files
changelog_begin
- [Daml Standard Library] Added function ``coerceInterfaceContractId``
changelog_end
* Added new method using contractUtil instead of filter so that creation of filter is not necessary in IouMain.
* public fields instead of private fields with getters
* delete getContracts
* var
* move ContractUtil to java binding
* to String
* update doc
* address comments
* address comment
* add change log
CHANGELOG_BEGIN
change quickstart java example to use typed acs stream and transaction.
CHANGELOG_END
* rename to response
* format
* update line number
* Expand the reference for the TypeScript library
The content is more or less there, I expanded some explanations and added a
reference to `create-daml-app`.
changelog_begin
changelog_end
* Fix link
* Update docs/source/app-dev/bindings-ts/index.rst
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* Update docs/source/app-dev/bindings-ts/index.rst
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* Update docs/source/app-dev/bindings-ts/index.rst
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
Co-authored-by: Jennifer Whyte <42810081+jwhyte-da@users.noreply.github.com>
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* Add intro page for off-ledger automation with Daml
This is meant as a page to introduce Daml Script (as an off-ledger automation
tool) and Daml Triggers. This will require this page to be added to the
table of contents in the appropriate place in a separate PR in the
documentation repository.
changelog_begin
changelog_end
* Apply suggestions from code review
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* Rephrase, reformat
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* pre
* address Stephen's comments
* get command from Update<R>
* to public
* generateDeprecatedFlattenedStaticExerciseByKeyMethod
* Ensure interface generation uses package prefixes
CHANGELOG_BEGIN
- [BUGFIX] Interface generation now respects package prefixes argument. This means generated interfaces will now be placed in the right subpackages.
CHANGELOG_END
* packagePrefixes
* fix what exercise* returning update breaks
* doc
* format
* WIP
* address comments
* compile
* added 2 utility methods in CommandClient for getting the result of submitted commands to demonstrate value of Update R
* address some comments
* update line number
* rename
* fold for create and exercise cases
* move transaction logic to fold
* revert config
* argTypeDecoder
* add internal api doc
* rename to Choice
* quickstart doc
* use update
* address comment
* address comment on compactability issue
* move abstract static class FoldUpdate<Z> to Update<>
* change command clients to use List<? extends HasCommands> instead of List<Command>
* move fold to update
* compare commands
* Update docs/source/app-dev/bindings-java/quickstart.rst
Co-authored-by: Raymond Roestenburg <98821776+ray-roestenburg-da@users.noreply.github.com>
* address comments
* address comments
* add changelog
CHANGELOG_BEGIN
- [Java codegen] Replace return type to Update<R> of exercise and create methods in Java codegen
CHANGELOG_END
Co-authored-by: Fayi Femi-Balogun <fayimora.femibalogun@digitalasset.com>
Co-authored-by: Raymond Roestenburg <98821776+ray-roestenburg-da@users.noreply.github.com>
This allows additional chapters to be added in the future without disrupting existing pages.
[CHANGELOG_BEGIN]
[CHANGELOG_END]
Co-authored-by: carrie-laben <91496516+carrie-laben@users.noreply.github.com>
* Remove mention of FunctionalDependencies as data-dependencies caveat
FunctionalDependencies in data-dependencies have been supported since #7698
changelog_begin
changelog_end
* Remove mention of advanced type system features as data-dependencies caveat
module DA.Generics and language extension DeriveGeneric have long been removed
from the language, and I couldn't think of other similar "advanced type
system features" that work for plain dependencies but not for data-dependencies.
* Extend list of data dependable extensions
The development of the Helm Chart halted after 1.18.x to make room
for other priorities, including a better documentation of operational
concerns as a way for users to bridge the gap we were originally
trying to fill with the Helm Chart. The pages remained in the
documentation as we were hoping for the feature to go back into
active development but since the feature is not actually working and
we do not have short term plans to revive it (and possibly not in
the current form) it is better to just yank the content until
we have a better understanding of where we want this to go.
If by any chance we want to restore the feature more or less in
its current form, restoring this document from a previous version
requires very little effort while simultaneously we do not cause
confusion by documenting a feature that does not work with the
current version.
changelog_begin
changelog_end
"ones whose values can be written in a text or binary format" is a very
misleading definition to give for "serializable types" in the context of
Daml.
When we say "serializable" in Daml, we *always* mean the formal Daml-LF
definition given in "Serializable types" in daml-lf-1.rst, i.e. ⊢ₛ τ, or
"τ derives from the rules S". That is also what we mean here.
There are many examples of types "whose values can be written in a text
or binary format", that are nevertheless *not* derivable from S.
As it says in daml-lf-1.rst, "serializable types are the types whose
values can be persisted on the ledger". So we copy over something like
that language.
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
* Provide an introduction to the Canton Console
The purpose of this page is to expose developers to the availability of the Canton Console
as part of the SDK to interact with the Sandbox, provide tips on how to consult the built-in
documentation and provide further pointers to the in-depth documentation page part of the
Canton user manual.
changelog_begin
changelog_end
* Apply suggestions from code review
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
Co-authored-by: carrielaben-da <91496516+carrielaben-da@users.noreply.github.com>
