Skip to content

Do not throw a ERR_INVALID_FIELD_REFERENCE exception if a field is not in current metadata #786

@dcrissman

Description

@dcrissman

Spun off from a discussion on #776

Summary of discussion:
The decision to throw an exception from metadata.resolve() was wrong. It produces unnecessary logs and will fail somewhere else.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions