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

fix: add ftl as a parser that can be enabled #797

Merged
merged 1 commit into from
Apr 29, 2023
Merged

fix: add ftl as a parser that can be enabled #797

merged 1 commit into from
Apr 29, 2023

Conversation

mrnossiom
Copy link
Contributor

Hi there,

the Fluent project support has been added with the fluent-vue support (#651). It works well, but VS Code still issues a warning saying that ftlis not a valid parser. It is useful for projects that use Fluent without a specific framework or in another language (Rust).

Thanks for your time

This schema definition says that `ftl`is not a valid parser, but it has been added with the `fluent-vue` support. It is useful for custom frameworks that use plain fluent project.
@JonL1
Copy link

JonL1 commented Mar 31, 2023

I'm also interested in this as I use i18next framework with a fluent backend. Is there anything holding back this PR? Can I help in any way?

@terales
Copy link
Collaborator

terales commented Apr 29, 2023

Closed/reopened the PR to trigger new CI checks

@terales terales merged commit 232da97 into lokalise:main Apr 29, 2023
@mrnossiom mrnossiom deleted the patch-1 branch April 29, 2023 11:51
huacnlee pushed a commit to huacnlee/i18n-ally that referenced this pull request Aug 28, 2023
This schema definition says that `ftl`is not a valid parser, but it has been added with the `fluent-vue` support. It is useful for custom frameworks that use plain fluent project.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants