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

use the same key for the filepath and basename use case #1

Open
regisphilibert opened this issue Feb 1, 2023 · 0 comments
Open

use the same key for the filepath and basename use case #1

regisphilibert opened this issue Feb 1, 2023 · 0 comments

Comments

@regisphilibert
Copy link
Member

Currently we're using two different keys which either/or to define where to save the markdown file.

Either you use basename to define the slug and the module will deduct the rest from the _content file location or filepath and we'll use this as is.

I think we should simplify the documenation by simply using one key (target or output) and test if an extension is present.
With extension: it's the filepath, use as is.
Without extension, it's the slug, deduct the filepath.

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

No branches or pull requests

1 participant