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

Error opening inlang project at ./project.inlang Error: Plugins for loadMessages (found: 1) and saveMessages plugins (found: 1) must not coexist with import (found: 1) or export (found: 1) #201

Open
samuelstroschein opened this issue Sep 18, 2024 — with Linear · 2 comments

Comments

Copy link
Member

Problem

The inlang message format v3 contains both load/save messages and import/export files because most users do not have a pinned plugin version. Any update to the inlang message format (and other plugins) will break usage if the old load/save messages are defined.

Proposal

  1. Allow defining both old load and save messages apis
  2. If import/export files is defined, ignore load/save messages
Copy link
Member Author

@felix.haeberle @martin.lysk1 i assume you ran into this too? agree with the proposal?

Copy link

felixhaeberle commented Sep 19, 2024

seems reasonable 👍 did not ran into this problem because only worked with i18next source files (json) and i18next old plugin.

  • how do we plan to do the phase-out strategy of the old APIs when allowing both?
  • switch to mandatory pinned version for plugins & deprecating them in inlang message v4?

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

2 participants