Output action urls during run/dev
- Dominant language
- JavaScript
- Stars
- 95
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
Developers report errors to us sometimes, and they are simply lacking information on what url to load to test their action code.
During run/dev we only output the frontend url, or if there is no frontend we actually do output the action urls ... we should not assume that whenever there is a frontend developers don't want to call the actions directly. We should just add this info to the output.
Something like:
```bash
To view your local application:
-> https://localhost:3000
To view your deployed application in the Experience Cloud shell:
-> https://experience.adobe.com/?devMode=true#/custom-apps/?localDevUrl=https://localhost:3000
Web action urls:
dx-excshell-1/generic - https://localhost:3000/api/v1/web/dx-excshell-1/generic
```
Contributor guide
Research direction
Start by locating the run/dev command's output handling and the existing path that prints action URLs when no frontend is present. Confirm the behavior with a local run/dev scenario; done means action URLs are also listed when a frontend URL is displayed, while the existing no-frontend output remains correct.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100