Skip to content

Unify wording and documentation to serve an IResource #535

Open
@Kaliumhexacyanoferrat

Description

@Kaliumhexacyanoferrat

As a developer using the GenHTTP framework, I would like to have a similar wording and functionality for something that serves a resource tree vs. the handler that serves a single resource.

Notes

Currently there is Resources and Content, which is misleading.

Acceptance criteria

  • The wording has been unified
  • The documentation has been unified

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions