FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Consider renaming field option `default` to `fallback` · Issue #120 · contentlayerdev/contentlayer · GitHub

Consider renaming field option default to fallback #120

Description

I'm currently considering renaming the field option default to fallback within the defineDocumentType or defineNestedType definitions in contentlayer/source-files.

Reasoning:
The term default value is typically used when "creating" some kind of record - however, Contentlayer never creates any kind of records/documents but just transforms then. Therefore I'm arguing the term fallback is more appropriate when considering the absence of a value.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


    Back | FazBrowse Home | New Git URL