fix/feat: named channels and interrupts

[mhier]

No description provided.

[phako]

I am a bit confused, so we did NOT support interrupted named channels, but were also missing the tests for what we supported?

[Copilot]

🟢 Approval recommended

The behavior change is narrowly scoped, consistent with existing access-mode semantics, and is covered by updated and new tests.

Pull request overview

This PR updates the JSON map parsing behavior so that named channel slices of interrupt-driven 2D registers inherit interrupt semantics (and thus support wait_for_new_data), while slices of non-interrupt 2D registers remain read-only and do not advertise wait_for_new_data.

Changes:

• Update JsonMapFileParser to mark named channel slices as INTERRUPT when their parent 2D register is interrupt-driven.
• Extend JSON map parser tests to assert correct access mode flags for interrupt vs non-interrupt named slices.
• Add a new non-interrupt 2D register with named channels to the test JSON map file to validate read-only slice behavior.

File summaries

File	Description
tests/simpleJsonFile.jmap	Adds a non-interrupt 2D register with named channels (SIMPLE2D) to exercise slice behavior.
tests/executables_src/testNumericAddressedBackendUnified.cpp	Adds an async named-slice unified-backend test for an interrupt-driven 2D register slice.
tests/executables_src/testJsonMapFileParser.cpp	Updates expectations: interrupt-driven 2D slices now advertise wait_for_new_data; adds coverage for non-interrupt 2D slice behavior.
src/JsonMapFileParser.cc	Implements access-mode propagation for named channel slices of interrupt-driven 2D registers.

Review details

• Files reviewed: 4/4 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.