Skip to content

Conversation

@jamesnw
Copy link
Collaborator

@jamesnw jamesnw commented Sep 30, 2024

Tiny QOL change- the first thing I want to do after running feature-init is open the newly generated file. This prints the path to the console, so I can click on it and open it.

@github-actions github-actions bot added the tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings label Sep 30, 2024
Copy link
Collaborator

@ddbeck ddbeck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One optional suggestion for you. Feel free to merge with or without it.

process.exit(0);
}
await fs.writeFile(destination, formatted);
console.log(`Wrote ${destination}`);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you write out just the file name, then it's possible to do something like this: my-editor $(npm run --silent feature-int -- …) or pipe it to another command, right?

Suggested change
console.log(`Wrote ${destination}`);
console.log(destination);

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call!

@jamesnw jamesnw merged commit 7203300 into web-platform-dx:main Sep 30, 2024
@jamesnw jamesnw deleted the feature-init-path branch September 30, 2024 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

tools and infrastructure Project internal tooling, such as linters, GitHub Actions, or repo settings

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants