Fix init command

[marcospassos]

Summary

This PR fixes issues with the init command when using the new option and resolves a bug that was preventing the CLI from detecting production applications.

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@112

commit: be1b6e9

[Copilot]

Pull Request Overview

This PR enhances the CLI init command and related form handlers to track newly created entities, refines slug generation, and adjusts publish logic in the GraphQL workspace API.

• Update GraphQL API publish flag logic and slug baseName for environments
• Extend form handlers to return a new flag via Selected* types
• Introduce resolveApplication in init command for smarter production application selection

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/infrastructure/application/api/graphql/workspace.ts	Simplify publish flag check; refine slug baseName conditional
src/application/cli/form/workspace/workspaceForm.ts	Return SelectedWorkspace with new flag
src/application/cli/form/organization/organizationForm.ts	Return SelectedOrganization with new flag
src/application/cli/form/application/applicationForm.ts	Return SelectedApplication with new flag and updated labels
src/application/cli/command/init.ts	Adjust init logic to use new flags and add resolveApplication

Comments suppressed due to low confidence (4)

src/application/cli/form/workspace/workspaceForm.ts:22

• [nitpick] Using a property named new can be confusing given it’s a reserved keyword; consider renaming it to isNew or createdNew for clarity.

export type SelectedWorkspace = Workspace & {

src/application/cli/form/organization/organizationForm.ts:20

• [nitpick] The optional new property may be mistaken for the keyword; renaming to isNewOrganization or createdNew would improve readability.

export type SelectedOrganization = Organization & {

src/application/cli/form/application/applicationForm.ts:27

• [nitpick] Consider renaming the new field to isNew or isNewApplication to avoid confusion with the JavaScript new keyword.

export type SelectedApplication = Application & {

src/application/cli/command/init.ts:227

• The new resolveApplication method introduces branching logic for production vs. development flows; consider adding targeted unit tests to cover scenarios where it returns null or invokes getApplication.

    private async resolveApplication(options: ApplicationOptions, applicationSlug?: string): Promise<Application|null> {

[Copilot]

The expression experience.draft !== true is equivalent to !experience.draft but may be less idiomatic; consider using publish: !experience.draft for clarity.

Suggested change

	publish: experience.draft !== true,
	publish: !experience.draft,