Repository navigation
Merge releases/r10.0 into develop (Hamza's r10.0 changes, ahead of the production release) - #374
Conversation
The Ingress exposed only /api and /swagger, so the admin SPA at / stayed on whatever else served the host unless every deployment remembered to add it. A deployment that tried (`ingress.path=/api, /`) found that `ingress.path` is ignored whenever `ingress.paths` is set, which it always is by default. ingress.paths now defaults to [/api, /swagger, /], and ingress.path, the fallback for an empty list, is / too. Gateway mode already routes / and renders unchanged.
…10.0 Chart: route / by default, alongside /api and /swagger (r10.0)
Upgrade SW-Bus to 10.0.2
Upgrade SW-Bus to 10.0.3
…lter Exchanges: property filter matches any part of the picked property's value
…h-button Exchanges: add a Refresh button
Brings Hamza's six commits that went straight to r10.0 (#352, #354, #356, #367, #369) into develop, so develop can be promoted to r10.0 without dropping them. Conflicts, resolved keeping both sides: - XchangeFilters.cs: develop's retry, scheduled-retry, aggregated and error-text filters, then r10.0's PromotedPropertyKey filter, which has to come before the value loop that searches inside that key's value. - exchanges.ts: r10.0's key-apart property terms, then develop's four new filters. - ExchangesPage.tsx: develop's redesigned page. r10.0's Refresh button and loading state are ported into it: Refresh sits in the Live control and reloads the list, counts and chart at once; a filter or page change, or Refresh, dims the list under a loading bar, while the background live ticks don't. - SW.Bitween.Web.csproj: develop's OpenTelemetry packages with r10.0's SimplyWorks.Bus 10.0.3. The other three projects took 10.0.3 without conflict. - docs/configuration.md: both new sections. - docs/deployment.md: develop's probe text, which describes the chart this branch ships. Two component tests added: Refresh asks again for the list and the counts while paused, and a picked property is sent apart from its value.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. 🗂️ Base branches to auto review (8)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Full .NET run against this merge (throwaway branch, since deleted): unit 799 passed, 7 skipped; integration 723 passed, 0 failed. That includes Hamza's |
r10.0 has six commits that went there directly and never reached develop (#352, #354, #356, #367, #369):
/route.Merging develop into r10.0 for the first production deploy conflicts with them. Done naively, it would drop them. This PR merges r10.0 into develop first, keeping both sides, so the promotion afterwards is clean.
@hamza @samer, please review the Exchanges parts: Hamza's fixes are ported into Samer's redesign.
How each conflict was resolved
XchangeFilters.csPromotedPropertyKeyfilter. The key filter has to come before thePromotedPropertiesRawloop, which searches inside that key's value; that part merged cleanly.exchanges.tsPromotedPropertyKey:1:<key>+PromotedPropertiesRaw:4:<value>), then develop's four new filters. Develop's QueryBar already keepspropertyKeyandpropertyas separate URL parameters and labels the chip "contains", so it matches the new server semantics without further change.ExchangesPage.tsxaria-busy); the background live ticks don't. Whitespace-insensitive: +42/−4.SW.Bitween.Web.csprojBus.RabbitMqExtensionstook 10.0.3 without conflict, so every project is on 10.0.3.docs/configuration.mdInitialAdminPassword,Bus:OnInvalidUserToken).docs/deployment.mddocs/operations.mddescribes Refresh in the Live control, beside Pause.Checked
tsc -bandoxlintare clean.vitest: 108 files, 688 tests pass, including two new ones:NODE_OPTIONS=--no-experimental-webstorage: Node's ownlocalStorageshadows jsdom's. CI uses Node 22.PromotedPropertySearchTestsand the other promoted-property integration tests are running separately against this merge; results will be added here.