* use domain.Party instead of String in jwtForParties, headersWithPartyAuth
CHANGELOG_BEGIN
CHANGELOG_END
* use domain.Party instead of String in headersWithPartyAuth
* fix sharedAccountCreateCommand and some corners
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>
* 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
