hyperweb-io / hyperweb-io/starship

feature: client port fowarding should be done by port name instead of port number

Open
#726 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
77
Forks
39
PR merge metrics
No merged PRs in 30d

Description

## Overview
If the port forwarding is done via port names, will become easier to host arbitry ports as well from local and remote.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by locating the client port-forwarding entry point and reading how it currently selects ports by number. Define the expected behavior for selecting ports by name and for arbitrary local and remote ports. Done means the client forwards named ports reliably in both local and remote cases, with tests covering the new behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, typescript
Domain
infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.