wasp-lang/wasp

Filter projects by `workspace` if provided

Open

#3430 opened on Nov 25, 2025

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

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

Tech stack
typescriptnodejs
Domain
clidevops
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
TypeScriptRailway CLI basicswasp deploy internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate alternative ways to filter Railway projects by workspace, as the `railway list` command currently lacks a ` workspace` flag. Look into using Railway's API directly or parsing the output of `railway list` to filter manually. Check the existing code in `waspc/data/packages/deploy/src/providers/railway/railwayProject/cli.ts` around line 124 where the list is used. Consider if the workspace information can be obtained from other commands or environment variables.