Fix daml.yaml example to match actual dpm init output - #1219
Draft
8bitpal wants to merge 1 commit into
Draft
Conversation
The documented example included sdk-version and build-options fields and different defaults for name/version/dependencies than dpm init (1.0.21) actually generates. Updated the example to match, and clarified in the key fields list that sdk-version and build-options are optional fields dpm init does not set, with sdk-version falling back to the globally active SDK version when absent. Signed-off-by: 8bitpal <elias@zerolimit.es>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Closes #1196.
The documented
dpm initexample daml.yaml didn't match actual output. Per the repro in the issue (dpm 1.0.21, SDK 3.5.3):vs. the documented example which had
sdk-version,name: my-project,version: 1.0.0, nodaml-scriptdependency, and abuild-optionsblock — none of whichdpm initactually generates.sdk-versionandbuild-optionsare valid daml.yaml fields but aren't set bydpm init; noted thatsdk-version, when absent, falls back to the globally active SDK version (dpm version --active).