Conversation
{pm} token--include-defaults flag to list commands and document {pm} token
Contributor
265d9e2 to
c260046
Compare
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
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.
Description
This PR introduces the
--include-defaultsoption to thedk listanddk config listcommands, allowing users to view Scaffolder's built-in, default settings and templates alongside their custom configurations.Additionally, this PR includes updated documentation to clarify the use of the new
{pm}token, which simplifies writing package manager-agnostic commands in template configurations.Key Changes
1. Add
--include-defaults (-d)Flagdk list [-d | --include-defaults]: When used, the output will merge and display all available templates, including the built-in Scaffolder defaults. This provides a complete view of all templates that can be used withdk new.dk config list [-d | --include-defaults]: Extends the detailed configuration view to include the Default configuration source, making it easier for users to debug configuration overrides and understand what settings/templates are provided out-of-the-box.2. Introduce and Document
{pm}Token{pm}can now be used in thelocationproperty of command-based template configurations (e.g.,{pm} create next-app@latest).packageManager> globaldefaultPackageManager> CLI default).README.md) has been updated to explain the purpose and usage of this token, promoting package manager-agnostic template definitions.Why This is Valuable
These changes enhance user control and transparency:
{pm}token allows users to define template commands that automatically adapt to their preferred package manager setting.Fixes # (issue)
Type of change
Checklist: