[Bug]: Inconsistent REST Path Validation Between `init` and `configure`

Open Beginner friendly
#3,535 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
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
cli

Research direction

Start with the dab init and dab configure command entry points and reproduce both path-validation behaviors from the issue. Trace where rest.path and runtime.graphql.path are validated, then run the relevant CLI tests or commands to confirm both reject or normalize paths consistently.

Written by the indexing model from the issue text.

Description

2.0 cli

Expected:

Both should behave the same, either reject or normalize consistently.

# This silently succeeds (prepends /):
dab init --database-type mssql --connection-string "test" --rest.path "noslash" --config test.json

# This correctly fails:
dab configure --runtime.graphql.path "noslash"
# fail: Path must start with a '/'
Dominant language
C#
Stars
1.5k
Forks
372
Avg merge
3d 8h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

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 Azure/data-api-builder

All issues in Azure/data-api-builder

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.