Skip to content

Consider wether to define target types #6

@zanerock

Description

@zanerock

Overview

From the docs:

The include target searched by import must match: '..sh'. The 'content type' is generally something like 'func' or 'inline', but is not currently standard.

Is there a use to recognizing certain target 'types'?

Deliverables

  • Either come up with an updated spec that recognizes different types (for a purpose) and how they are handled or specify that the type is useful for file organization, but ignored.
  • Even if ignored (or otherwise non-functional) suggest standard types like func, funcs, and inline.

Notes

Possible use cases:

  • foo.inline-always.sh triggers unavoidable/baked-in bash-rollup-always-inline behavior.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs specTask not fully specified

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions