Skip to content

feat(tinylicious): Support command line --port argument#27709

Draft
Josmithr wants to merge 2 commits into
microsoft:mainfrom
Josmithr:tinylicious/command-line-port-argument
Draft

feat(tinylicious): Support command line --port argument#27709
Josmithr wants to merge 2 commits into
microsoft:mainfrom
Josmithr:tinylicious/command-line-port-argument

Conversation

@Josmithr

@Josmithr Josmithr commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Adds a --port argument to the tinylicious command. Previously, the only way to configure the port tinylicious used was via an environment variable. Now, a command line argument is supported as well (and takes precedence over the environment variable when both are set).

This is part of a multi-PR effort to allow our repo's tinylicious real service tests to get port assignments dynamically.

This library update needs to be published before the changes can be used in the client packages for their tinylicious tests. But the whole story can be previewed here: #27701.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 2 pipeline(s).
13 pipeline(s) were filtered out due to trigger conditions.
Some pipeline(s) encountered errors during trigger evaluation.

@github-actions

Copy link
Copy Markdown
Contributor

Bundle size comparison

Base commit: e1dcf16db76b2c217bf3bd9e5de80eabc8e68ce8
Head commit: 86122a4035a6cae263c09924336568cff2e3acc3

Pending — Build - client packages is running. Results will appear here when the build completes.

@github-actions

Copy link
Copy Markdown
Contributor

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (65 lines, 3 files), I've queued these reviewers:

  • Correctness — logic errors, race conditions, lifecycle issues
  • Security — vulnerabilities, secret exposure, injection
  • API Compatibility — breaking changes, release tags, type design
  • Performance — algorithmic regressions, memory leaks
  • Testing — coverage gaps, hollow tests

How this works

  • Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

  • Tick Start review below to dispatch the review fleet.

  • After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

  • This comment updates as new commits land; your reviewer selections are preserved.

  • Start review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant