Add validation step on stack_name

Open Beginner friendly
#2,013 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cli

Research direction

Locate the CLI code that performs the stack_name step and inspect any existing validation tests; no file or test path is named in the issue. Run the relevant test suite, then verify that uppercase characters are rejected immediately after the stack_name step while lowercase alphanumeric names remain accepted.

Written by the indexing model from the issue text.

Description

The stack name validation should fail immediately after the stack_name step if the name is invalid. Right now it only rejects non-alphanumeric characters, but it still allows uppercase letters. We should also reject uppercase characters so that stack names are limited to lowercase alphanumeric characters only.

Image Image
Dominant language
Go
Stars
166
Forks
24
Avg merge
10h 8m
Merged PRs (30d)
33

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DefangLabs/defang

All issues in DefangLabs/defang

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.