fix: make upstream optional in backend-api7 typing

[jarvis9443]

Summary

Make the upstream field optional in the Service interface of backend-api7 typing.

A service may not always have an upstream — for example when using service discovery or plugin-only services. The transformers (ToADC.transformService and FromADC.transformService) already guard against undefined upstream with conditional checks, so the type definition was out of sync with the runtime behavior.

Changes

• libs/backend-api7/src/typing.ts: Changed upstream: Upstream to upstream?: Upstream

Testing

All existing backend-api7 tests pass (npx nx test backend-api7 — 8/8 tests passed).

Summary by CodeRabbit

• Improvements
  • Service configuration is now more flexible with upstream settings made optional. This reduces required configuration steps and allows services to be created with fewer mandatory fields.

[coderabbitai]

📝 Walkthrough

Walkthrough

The upstream property in the Service interface has been made optional, changing from a required field to an optional configuration parameter. This allows Service objects to be instantiated without specifying an upstream value.

Changes

Cohort / File(s)	Summary
Type Definition libs/backend-api7/src/typing.ts	Made upstream property optional in Service interface by changing from upstream: Upstream to upstream?: Upstream.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 An optional upstream path we see,
A property now wild and free,
Configurations light as air,
Services need not always care! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'fix: make upstream optional in backend-api7 typing' directly and clearly summarizes the main change: making the upstream property optional in the Service interface type definition.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/optional-upstream

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[CLAassistant]

All committers have signed the CLA.

[bzp2010]

This will only apply to the development process; this identifier will not affect runtime behavior in any way, as compilation will result in type erasure. In other words, it simply informs developers that the value might be null and throws an error if there is a type mismatch. If anyone chooses to ignore it, this is of no use.

In any case, this is a positive change.