Skip to content
This repository has been archived by the owner on Nov 5, 2021. It is now read-only.

Why Do The Docs Specify Eta v1.6.0 #67

Open
shadowtime2000 opened this issue Nov 5, 2020 · 5 comments
Open

Why Do The Docs Specify Eta v1.6.0 #67

shadowtime2000 opened this issue Nov 5, 2020 · 5 comments
Assignees
Labels
Priority: Medium Type: Question This item is seeking an answer

Comments

@shadowtime2000
Copy link

Summary

Hi 👋

I am one of the maintainers of the Eta template engine. I am just wondering why in the documentation for using it is the import importing v1.6.0 when v1.11.0 is the latest.

@crookse crookse added Priority: Medium Type: Question This item is seeking an answer labels Nov 5, 2020
@crookse crookse self-assigned this Nov 5, 2020
@crookse
Copy link
Member

crookse commented Nov 5, 2020

Hi @shadowtime2000,

The Eta documentation says v1.6.0. We can have this updated though on our end so as not to confuse users.

@shadowtime2000
Copy link
Author

@crookse Sounds good, I will look at updating the documentation in the Eta site too.

@crookse
Copy link
Member

crookse commented Nov 7, 2020

@shadowtime2000, where are the docs to using Eta v1.11.0? Or is it that the docs will just reflect a version bump? If it's just a version bump, then I'll update Eta to v1.11.0 and will have the PR ready to be merged to reflect the change.

@shadowtime2000 shadowtime2000 changed the title Why Do The Docs Specify Eta v0.1.6.0 Why Do The Docs Specify Eta v1.6.0 Nov 7, 2020
@shadowtime2000
Copy link
Author

shadowtime2000 commented Nov 7, 2020

@crookse I have updated the documentation on the page you referenced.

@crookse
Copy link
Member

crookse commented Nov 8, 2020

@shadowtime2000, ahh so it was just a version bump. ok cool! i wasn't sure if Eta had different docs pages for each version. i will get our docs updated first thing tomorrow. thanks again!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Priority: Medium Type: Question This item is seeking an answer
Development

No branches or pull requests

2 participants