Improve api key flow

[marcospassos]

Summary

This PR optimizes the API key creation flow to avoid prompting the user for environments that don’t exist.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

[github-actions]

👋 @marcospassos
Thanks for your contribution!
The approval and merge process is almost fully automated 🧙
Here's how it works:

1. You open a new pull request
2. Automated tests check the code
3. Maintainers review the code
4. Once approved, the PR is ready to merge.

👉 Omit the extended description
Please remove the commit body before merging the pull request.
Instead, include the pull request number in the title to provide the full context
about the change.

☝️ Lastly, the title for the commit will come from the pull request title. So please provide a descriptive title that summarizes the changes in 50 characters or less using the imperative mood.
Happy coding! 🎉

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/croct@113

commit: ce0fcbc

[Copilot]

Pull Request Overview

This PR refactors the API key creation flow to avoid prompting the user for environments that aren’t configured and centralizes environment-to-slug resolution.

• Extracts environment selection and slug lookup into getEnvironment and getApplicationSlug methods
• Defaults to development if production isn’t configured
• Imports ProjectConfiguration to type the new helpers

Comments suppressed due to low confidence (1)

src/application/cli/command/apiKey/create.ts:144

• Add unit tests for getEnvironment to cover: 1) automatic DEV fallback when production missing, 2) user prompt path when both environments exist.

        return input.select({

[Copilot]

[nitpick] Consider declaring this method as async rather than returning Promise.resolve(...), which improves readability and consistency with its asynchronous usage.

Suggested change

	private getEnvironment(
	configuration: ProjectConfiguration,
	environment?: ApplicationEnvironment,
	): Promise<ApplicationEnvironment> {
	if (environment !== undefined) {
	return Promise.resolve(environment);
	}
	if (configuration.applications.production === undefined) {
	return Promise.resolve(ApplicationEnvironment.DEVELOPMENT);
	}
	const {io: {input}} = this.config;
	return input.select({
	private async getEnvironment(
	configuration: ProjectConfiguration,
	environment?: ApplicationEnvironment,
	): Promise<ApplicationEnvironment> {
	if (environment !== undefined) {
	return environment;
	}
	if (configuration.applications.production === undefined) {
	return ApplicationEnvironment.DEVELOPMENT;
	}
	const {io: {input}} = this.config;
	return await input.select({

[Copilot]

If both production and development are undefined, this code will default to DEVELOPMENT and only later throw—consider adding a guard here to surface a clear error when no environments are configured.

Suggested change

	if (configuration.applications.production === undefined
	&& configuration.applications.development === undefined) {
	throw new HelpfulError(
	'No environments are configured in the project. Please configure at least one environment.',
	{reason: ErrorReason.INVALID_INPUT},
	);
	}