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

Deprecate Nunjucks and Create Migration Guide to React #1255

Open
Gmin2 opened this issue Aug 16, 2024 · 3 comments
Open

Deprecate Nunjucks and Create Migration Guide to React #1255

Gmin2 opened this issue Aug 16, 2024 · 3 comments
Assignees

Comments

@Gmin2
Copy link
Collaborator

Gmin2 commented Aug 16, 2024

We're planning to depreciate Nunjucks in favor of React for our templating system. This issue is to create a comprehensive migration guide and outline our deprecation process.

  1. Migration Guide:

  2. Gradual Deprecation:

    • We'll start by adding deprecation warnings to all Nunjucks-related features.
    • Each Nunjucks feature will be marked for removal in future versions.
    • The timeline for removing each feature is mentioned below.
  3. React Alternatives:

    • For each deprecated Nunjucks feature, we have provided a React-based alternative in the migration guide.
    • Examples is included in the guide to show how to achieve the same results with React.
  4. Documentation Updates:

    • All mentions of Nunjucks in our docs will be updated to reference the deprecation.
  5. User Communication:

    • We'll encourage users to start migrating their templates and provide feedback.
  6. Timeline:

    • Deprecation warnings added: []
    • Begin removing Nunjucks features: []
    • Complete removal of Nunjucks support: []
@Gmin2 Gmin2 converted this from a draft issue Aug 16, 2024
@Gmin2 Gmin2 changed the title Research how to deprecate nunjucks Depreciating Nunjucks Aug 16, 2024
@Gmin2 Gmin2 changed the title Depreciating Nunjucks Deprecate Nunjucks and Create Migration Guide to React Aug 16, 2024
@derberg
Copy link
Member

derberg commented Aug 21, 2024

We'll start by adding deprecation warnings to all Nunjucks-related features

what do you mean? in case of cli.js it is easy as we will drop a message in cli, but in case of nunjucks features?

Each Nunjucks feature will be marked for removal in future versions.

what is your proposal on how to do that?

Timeline

I'm guessing timeline is the same as for CLI deprecation? 1.09?

@toffee-k21
Copy link

I like this idea. I want to take part and contribute to this transition, please tell me that I have to do it in only one single PR ?

@Gmin2
Copy link
Collaborator Author

Gmin2 commented Sep 16, 2024

I like this idea. I want to take part and contribute to this transition, please tell me that I have to do it in only one single PR ?

Hey @toffee-k21, there is nothing need to be done here accept for depreciation notice, you can look up to some other issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

3 participants