Skip to main content
Knowledge mapBuild and check a providerArcBlock

You are here. See how this question connects to other ideas.

Select a node to open its page · Expand to read within the map

Knowledge mapFollow a connection. Understand a question.
← AFS

Learning path

Build and check a provider

From path contracts to reads, actions and conformance tests.

This path reuses connected lessons. Follow the sequence or enter through any question below; examples and capability boundaries live in each lesson.

Along this path

  1. Should a provider return its mount prefix?

    Providers use their own relative paths; the dispatcher restores the mount prefix.

  2. How do you start a read-only provider?

    Begin with one explicit resource and its path contract before adding operations.

  3. How do you expose a discoverable action?

    An action needs discoverable arguments, effects and failures as well as a handler.

  4. What do conformance tests establish?

    Check declared shared contracts, not merely whether a demonstration runs.

  5. Check a read-only provider

    Mount a report at /work and check it with shared tests and an actual read.

  6. Why test rejection as well as success?

    Success-only examples miss over-broad access, swallowed errors and lost updates.