wasp-lang/wasp

Filter projects by `workspace` if provided

Open

#3,430 opened on Nov 25, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Haskell (227 forks)batch import
bugf: deploymentf: deployment [railway]good first issue

Repository metrics

Stars
 (4,229 stars)
PR merge metrics
 (Avg merge 1d 10h) (88 merged PRs in 30d)

Description

Users can provide the workspace option to the wasp deploy railway launch command. We don't use that information to more precisely return the list of Railway projects here.

This will be helpful for #2926 since we'll be able to be more precise in our checks if a Railway project exists or not in the selected workspace.

As of 2026-04-16, the Railway CLI doesn't provide a --workspace or similar flag for the railway list command, so there's not an easy way to do this.

Contributor guide

Research direction
Check if the Railway CLI now supports a ` workspace` flag for `railway list`. If not, consider parsing the output of `railway list` to filter by workspace name or ID, or use the Railway API directly.
Tech stack
typescriptnodejs
Domain
backendclidevops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Unclear
Prerequisites
Node.jsRailway CLI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50