-
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
DAML-LF: factorize ScenarioNodeId and EventId #6256
Conversation
6070905
to
4763831
Compare
CHANGELOG_BEGIN CHANGELOG_END
4763831
to
4fd18d9
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.
LGTM but I'm a bit concerned about having //daml-lf/interpreter
as a direct dependency of the sandbox.
ledger/sandbox/src/test/lib/scala/com/digitalasset/platform/store/dao/JdbcLedgerDaoSuite.scala
Outdated
Show resolved
Hide resolved
@@ -225,6 +225,7 @@ da_scala_library( | |||
"//daml-lf/archive:daml_lf_archive_reader", | |||
"//daml-lf/archive:daml_lf_dev_archive_java_proto", | |||
"//daml-lf/data", | |||
"//daml-lf/interpreter", |
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.
//daml-lf/interpreter
is where Speedy lives, right? Does it make sense for it to be a direct dependency of the sandbox? Any chance we can keep those separated?
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.
Moving into the sandbox in the current state, it is clearly not an option.
However, If you are keen on dropping this dependency, I could move the data type definition in "//daml-lf/transaction" (which is a fair dependency) in an upcoming PR.
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.
Makes sense thanks, I created #6260 so that you can use it to track it in the the upcoming PR you mentioned.
Sandbox and Scenario-service share the notion of
ScenarioNodeId
andEventId
but used different type.This PR makes the sharing explicit but dropping the
ScenarioNodeId
and using a commonEventId
that also make explicit the
TransactionId
andNodeId
component in theEventId
.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.