python: Make type string identifiers more consistent with the HTTP JSON API #90
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make type string identifiers more consistent with the HTTP JSON API.
A few under-the-hood changes, none of which should break typical application code but may impact code that uses
dazl
's DAML reflection capabilities:dazl.damlast.daml_lf_1
formerly depended ondaml.model.types
, as some long-existing types (notablyTypeReference
) were repurposed for parsing DAML-LF Archives. This dependency has now been flipped in order to makedazl.damlast.daml_lf_1
function more as a standalone package (and to pave the way for code generation of this file instead of manually maintaining its contents).dazl.model.types.TypeReference
used to be equivalent todazl.damlast.daml_lf_1.TypeConName
and were used interchangeably (because they were the same type). This has changed, anddazl.model.types.TypeReference
now wrapsdazl.damlast.daml_lf_1.TypeConName
.PackageRef
,ModuleName
, andDottedName
are now considered private implementation details as a future version ofdazl
will be changing under-the-hood details.This addresses #84.