Reject wrong workspace URL when creating a new one
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 146
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
When you create some "stuff" on Mashlib, it often requires a "workspace" to store the data.
Normally, you also create your workspace on the same UI -- I did not find a different place to do this.
When creating the workspace, you need to specify the URL of your workspace.
It currently accepts anything (as far as I tried), so it gave me the impression that it can automatically resolve relative paths.
However, in fact, when creating the "stuff", it will reject such scenarios, and reminds you that only absolute URIs/URLs are accepted.
It would be ideal if validating/checking and alerting happens when creating the workspace. If not totally possible, it should at least reject the obviously wrong ones (e.g. relative paths; non-URLs).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the workspace-creation form and trace how the workspace URL is accepted before a new workspace is created. Check how later workspace usage rejects invalid values, then add validation or rejection for relative paths and other non-absolute URLs. Done means invalid workspace URLs are caught during creation with a clear alert.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100