liquid-labs / liquid-labs/bash-rollup
Consider wether to define target types
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
## 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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the documented include-target pattern and the listed use case for foo.inline-always.sh. Define whether target types have behavior or are only organizational, then document the decision, handling rules, and standard names such as func, funcs, and inline.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100