Skip to content

Spec compliance #6

@vwkd

Description

@vwkd

The specification contains imprecise definitions like "optional but strongly recommended" or "very optional". How do we deal with that? Currently, the "optional but strongly recommended" properties home_page_url and feed_url are typed as required though inputs aren't validated yet so one can pass anything if one ignores the TypeScript errors. We should clearly document the imprecise specification and any deviations from it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingdocumentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions