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

"bridgetown plugins new" produces old code #917

Open
surrim opened this issue Sep 11, 2024 · 1 comment
Open

"bridgetown plugins new" produces old code #917

surrim opened this issue Sep 11, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@surrim
Copy link

surrim commented Sep 11, 2024

bridgetown plugins new seems to produce old code:

spec.add_dependency "bridgetown", ">= 1.2.0", "< 2.0"

Bridgetown Version:
bridgetown 2.0.0.beta2 "(TBD!)"

To Reproduce

bridgetown plugins new test
tail test/test.gemspec

Current behavior
The command builds a plugin based on old standards and excludes Bridgetown 2.x. For example it uses Liquid instead of ERB:

cat test/layouts/test/layout.html
cat test/content/test/example_page.md

Expected behavior
The command should generate erb code by default or provide a parameter to set the template language. The accecpted version should include 2.0.

@surrim surrim added the bug Something isn't working label Sep 11, 2024
@jaredcwhite
Copy link
Member

Thanks for mentioning this @surrim. There's always a bit of a lag time between when the first betas go out and the new plugin repo is updated for final release. This has been on my personal todo list but it's good to track it an issue publicly. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants