Skip to content

Configurations should work without explicit package clause #13

@shykes

Description

@shykes

Currently even a simple cue configuration cannot be evaluated without a package clause. It doesn’t matter what the package name is, it just needs to exist.

In the interest of reducing the barrier to entry, we should reduce the cognitive load of a basic working configuration to a minimum. Since this mandatory package clause does not convey any useful information, we should make it optional, and not use one in example configurations.

NOTE: when creating a reusable cue package with the goal of importing it, of course it should always have a package clause in order for import to work.

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