Inconsistent empty-namespace handling in section view fetching causes wrong API requests and cache/key divergence

[adityathebe]

In src/pages/views/hooks/useAggregatedViewVariables.ts, the section query function fetches with section.namespace || "default" while the React Query key uses section.namespace and sectionData map keys use ${section.namespace ?? ""}:${section.name}; ViewContent then looks up with empty-string fallback. This creates a mismatch where sections with missing namespace are represented as "" in keys/lookups but fetched as "default" in /api/view/{namespace}/{name} paths, causing incorrect namespace requests for views not in default, plus duplicate or missed cache behavior/invalidation due to "" vs "default" key divergence for the same logical section.

[coderabbitai]

🔗 Related PRs

#2739 - feat: view sections [merged]
#2766 - fix: View sections in config details page [merged]
#2784 - fix: missing variables in view section [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!