Misleading error when running shore in folder that doesn't have main.pipeline.jsonnet
- Dominant language
- Go
- Stars
- 21
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
### Pre Requisites
* [ ] Put an X between the brackets on this line if you have done all of the following:
* Checked the FAQs on the message board for common solutions:
* Checked that your issue isn't already filed:
### Description
Original Author: @slonokot
``` shell
shore render
env variable `SHORE_PROJECT_PATH` is not set
```
### Steps to Reproduce
1.
2.
3.
**Expected behavior:**
**Actual behavior:**
**Reproduces how often:**
### Versions
### Additional Information
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue by running `shore render` in a folder without `main.pipeline.jsonnet`; the payload reports the current `SHORE_PROJECT_PATH` error. Then locate the CLI path that handles a missing project file and clarify the expected error behavior before changing it. Done means the command reports the missing project configuration accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100