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.

Sign up for GitHub

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

Jump to bottom

Feature: Support non-JSON formats #2

Open
radiovisual opened this issue May 31, 2024 · 0 comments
Open

Feature: Support non-JSON formats #2

radiovisual opened this issue May 31, 2024 · 0 comments

Comments

@radiovisual
Copy link
Owner

Currently the only translation file format that can be validated is JSON. But it would be nice if other formats could also work like XML, or properties files. I imagine the routine could just convert all supported file types to JSON so that the rule logic does not have to be customized for each file type.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@radiovisual