Skip to content

Hierarchical data configuration in YAML (via Aeson)#9

Merged
srid merged 10 commits intomasterfrom
meta-aeson
May 17, 2021
Merged

Hierarchical data configuration in YAML (via Aeson)#9
srid merged 10 commits intomasterfrom
meta-aeson

Conversation

@srid
Copy link
Copy Markdown
Owner

@srid srid commented May 16, 2021 •
edited
Loading

  • Extend this PR to support a more general 'data files' usage
    • ./foo/bar.yaml specifies the default meta for all notes under ./foo/bar/
    • Likewise, ./index.yaml specifies the global config, and include things like siteTitle
      • which one may override on a folder-basis, eg: ./sub-site.yaml may specify different title, etc.
  • refactor

@srid srid changed the title Aeson'ify Markdown frontmatter WIP: Aeson'ify Markdown frontmatter, etc. May 16, 2021
@srid srid marked this pull request as draft May 16, 2021 21:13
@srid
Switch from HsYaml -> yaml
f16d08a 
The 'tags' feature in template is broken. cf. snapframework/heist#128

One way to address it is to specify a frontmatter.yaml default for Aeson.Value, to ensure that all fields are present regardless of what's in the individual Markdown file.
@srid srid marked this pull request as ready for review May 17, 2021 04:02
@srid srid changed the title WIP: Aeson'ify Markdown frontmatter, etc. Hierarchical data configuration in YAML (via Aeson) May 17, 2021
@srid srid merged commit f52c341 into master May 17, 2021
@srid srid deleted the meta-aeson branch May 17, 2021 04:13
@srid srid mentioned this pull request May 19, 2021
Closed
shivaraj-bh pushed a commit to shivaraj-bh/emanote that referenced this pull request Dec 18, 2023
@srid
Merge pull request srid#9 from srid/meta-aeson
4dc4491 
Hierarchical data configuration in YAML (via Aeson)
This was referenced Apr 25, 2026
Closed
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@srid