Skip to content

feat(poly create base, component): exit with fail code if brick already exists#431

Merged
DavidVujic merged 3 commits into
mainfrom
issue-430-unique-brick-names
Mar 3, 2026
Merged

feat(poly create base, component): exit with fail code if brick already exists#431
DavidVujic merged 3 commits into
mainfrom
issue-430-unique-brick-names

Conversation

@DavidVujic
Copy link
Copy Markdown
Owner

@DavidVujic DavidVujic commented Mar 3, 2026

Description

Validate the brick name when running poly create component and poly create base. If a brick with the same name already exists, exit with a fail code.

Motivation and Context

fixes #430

How Has This Been Tested?

✅ CI
✅ Local run of the create base and create component commands using the CLI
✅ Local run of the create base and create component commands using the Poetry plugin

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

@DavidVujic DavidVujic force-pushed the issue-430-unique-brick-names branch from 70f4377 to af81dde Compare March 3, 2026 20:16
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented Mar 3, 2026

@DavidVujic DavidVujic merged commit ece7e33 into main Mar 3, 2026
4 checks passed
@DavidVujic DavidVujic deleted the issue-430-unique-brick-names branch March 3, 2026 20:26
@DavidVujic DavidVujic changed the title fix(poly create base, component): exit with fail code if brick already exists feat(poly create base, component): exit with fail code if brick already exists Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

poly check should validate that components and bases have unique names

1 participant