* 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>
* slf4j-api:1.7.36, logback:1.2.11
CHANGELOG_BEGIN
CHANGELOG_END
* Use HikariCP 4.x, as 5.x pulls in slf4j-api 2.x as well
* Revert Hikari CP to 3.4.5 since 4+ brings slf4j-api 2+
Co-authored-by: Tudor Voicu <tudor.voicu@digitalasset.com>
* move resolveTemplateId to ContractTypeIdMap
* replace the contractTypeIdMap with an interfaceIdMap
* remove ResolveContractTypeId's type parameter, replace with Overload relation
* define the ContractTypeId resolver to be overload, ctid-type-sensitive
* remove AnyKind usages
* remove resolveTemplateId argument-passing
* demonstrate very strange inserted cast
`x.packageId` inserts a cast on `x` to `ContractTypeId.Template`, for
which there is no local evidence
* fix compiler-inserted cast problem
- Why does this fix it? Who knows!
* failure of template ID resolution no longer fails later than we want
* fix resolution of interface IDs for websocket queries
CHANGELOG_BEGIN
- [JSON API] Some error messages have been corrected to no longer
confuse interface IDs with template IDs, based on what varieties of
contract type ID the endpoint in question supports.
CHANGELOG_END
* mention #15293 where relevant
* define templateId_ generically
* remove unused utilities for old resolver
changelog_begin
changelog_end
Status quo:
ledger-api-domain's domain object contained three classes related to parties:
1. `PartyDetails`, the oldest, which didn't contain the metadata field and was used both in client and indexer code,
2. `ParticipantPartyDetails`, added recently during the participant-local metadata extensions, similar to the `PartyDetails` above but additionally contains the metadata field,
3. `PartyRecord` which held participant-local metadata extensions for a party.
Changes:
1) `PartyDetails` gets renamed to `IndexerPartyDetails` and together with `PartyEntry` gets moved to participant-state-index Bazel package and is removed from client code,
2) `ParticipantPartyDetails` gets renamed to `PartyDetails` and is now used in the client code instead.
3) `PartyRecord` gets moved to participant-local-store Bazel package
* domain.ContractTypeId.Template
* ResolveKeyType to use .Template
* CreateAndExerciseCommand to use .Template
* keyTypeMap
* bitraverse
CHANGELOG_BEGIN
CHANGELOG_END
Co-authored-by: Stephen Compall <stephen.compall@daml.com>
* rename ChoiceMetadata to Choice
CHANGELOG_BEGIN
- [Java codegen] The (new since 2.4) ``ChoiceMetadata`` class has been
renamed to ``Choice``.
CHANGELOG_END
* replace ChoiceMetadata with Choice in codegen docs
* Document how to add a new item in the table of contents
changelog_begin
changelog_end
* Add link to instructions to make changes to the next unreleased version
* Point to fixed GHC
* Fix daml-test-files for improved GHC errors
* Fix error message to match critical parts of improved GHC errors
* satisfy changelog
CHANGELOG_BEGIN
CHANGELOG_END
* point to updated GHC
* Point to updated GHC
* Fix damlc tests for new GHC error messages
* Point to updated GHC
* Rename test //daml-script/export/integration-tests/golden:{export-=>}values
* Switch 'daml_ledger_export_test' to use 'run' instead of 'run-legacy-cli-config'
* Extract 'encodeImports' from 'encodeModuleHeader'
* Sort import list in 'daml ledger export'
* Add 'dev' argument to 'daml_ledger_export_test'
* Add interfaceId to ExercisedSelector
* Extract 'encodeExercisedEvent' from 'encodeCmd'
* Split 'encodeCid' into 'encodeCid{Expr,Pat}'
* 'CreatedContract' field 'tplId' now has type 'TemplateId'
* Specialize CreatedContract{=>WithPath}
* 'treeEventCreatedConsumedCids' returns Seq[SimpleCreatedContract] instead of Set[ContractId]
* Change type of 'SimpleCommand' field 'contractId' to 'SimpleCreatedContract'
* Coerce ContractIds to underlying template type
* Use interface ContractId in encodeExercisedEvent if present
* Add test //daml-script/export/integration-tests/golden:interface-choices
* Fix encoding of getAnyChoiceTemplateTypeRep in daml-script converter
* Set getAnyChoiceTemplateTypeRep to interfaceId if available
* fromExercised uses choice instead of templateId to find subtree
fromExercised uses exercised.argument.templateTypeRep instead of exercised.contractId.templateId
Previously it used exercised.contractId.templateId, but now it uses
exercised.argument.getAnyChoiceTemplateTypeRep, which corresponds
to the TemplateTypeRep of the {template,interface} that defined the choice.
* TestData.Exercised now takes a more flexible TestData.Choice argument
* Add unit tests for encoding of exercise of interface choice
* Apply code review suggestions
* sealed {trait=>abstract class} CreatedContract
* Use List instead of Seq
* Use ::= instead of :+= and ++=
changelog_begin
- [Daml export] Added support for interface choices (#15189)
- [Daml export] Export.daml imports are now sorted alphabetically
changelog_end
Co-authored-by: Stephen Compall <stephen.compall@daml.com>
* InMemUserMngtImpl: Introducece custom in-mem user repr to better handle resource versions. Fix not updating isDeactivated property
* Generalize concurrent change control tests for users and party records
* Move backend files such that related localstore files are separated from other files
* Remove unneeded nesting in ParticipantParty object
* Document rights in revoke/grant requests as optional. More conformance tests for users rights
changelog_begin
changelog_end
I started with wanting to remove the warning on incomplete pattern
match, thinking example code should be "good". Then I decided I should
skim the corresponding docs to check if that warning, or the pragma,
were actually mentioned in the text.
It turns out the warning should be there, but the pragma is not
explained and not necessary to get the warning. So the pargma can go.
But in the process I noticed a couple things that I belive can be
improved in the wording of the document, so I went agead and made a few
changes.
CHANGELOG_BEGIN
CHANGELOG_END
* remove accessor references from the decision branches of extractor
CHANGELOG_BEGIN
CHANGELOG_END
* eta-reduce all recursively-summoned ValueDecoders
* add more whitespace
