Skip to content

Changes to support spec v0.6.0 compliance #125

@toddbaert

Description

@toddbaert

⚠️ 0.6.0 should probably be undertaken only after the existing 1.0-functional requirements are complete.

Implement specification v0.6.0 changes

See changes since last release.

Please note there's no need to complete all these tasks in a single PR (in fact, that's not recommended). Consider creating a new sub issue for each of the below requirements.

Functional requirements:

Non-functional requirements:

  • add relevant tests
  • add examples and documentation, see template README
  • update specification badge to v0.6.0: Specification

Keep in mind:

  • backwards compatibility is highly encouraged
    • take every precaution to ensure existing code written by application authors and existing providers implementations, do not break
  • it's recommended these features are released together

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy