Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: allow atom layout module names #108

Merged
merged 1 commit into from
Oct 11, 2024

Conversation

halostatue
Copy link
Contributor

String values for layout module names are required to be supported in
the front matter, but it feels odd to require that they be strings in
config. This enables the specification of layout modules as atoms and
fixes a bug in PageExtension which required a layout value in the
front matter at all times.

@mhanberg
Copy link
Collaborator

Could you write a test for this? I think you might be able to just add a layout default (as an atom) to one of the extensions in that test and then remove the explicit layout from one of the test markdown files being written to disk in that test.

@mhanberg
Copy link
Collaborator

beautiful, just rebase on main and i'll get this merged.

thanks a lot!

String values for layout module names are required to be supported in
the front matter, but it feels odd to require that they be strings in
config. This enables the specification of layout modules as atoms and
fixes a bug in PageExtension which required a layout value in the
front matter at all times.
@mhanberg mhanberg merged commit c128593 into elixir-tools:main Oct 11, 2024
7 checks passed
@mhanberg
Copy link
Collaborator

thanks!

@halostatue halostatue deleted the allow-atom-layouts branch October 11, 2024 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants