metalsmith / metalsmith/metadata
Move entries to options.entries, provide parsers option
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 40
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
Similar to @metalsmith/sass and @metalsmith/js-bundle use the entries option.
Similar to @metalsmith/markdown's render option, provide a parse option
metalsmith.use(
metadata({
entries: {
nav: 'src/nav.yml',
featured: 'src/featured.yml'
},
parse: {
'.yml': customYamlParser,
'.csv': csvParse
}
})
)
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
Compare the option patterns in @metalsmith/sass, @metalsmith/js-bundle, and @metalsmith/markdown, which the issue references. Trace the metadata plugin's current options and file-loading entry point, then verify that entries are nested under options and that parse handlers can be selected by extension. Done means the shown YAML and CSV configuration is supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100