Skip to content

import shouldn’t have a default field #313

@wooorm

Description

@wooorm

Subject of the issue

Currently, both the import and export node have a default field. There is code to set the default field to true or false on export nodes, but the current code never sets import.default too true. So why does it exist?

Steps to reproduce

default: isExportDefault(subvalue),

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