-
Notifications
You must be signed in to change notification settings - Fork 0
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
If filename doesn't have .atf
extension, validation/lemmatisation of an invalid file never returns errors
#99
Comments
Eleanor suggests enforcing the |
Would this happen in normal (non-development) use? Isn't the extension "disabled" if the file name doesn't end in |
When you create a new empty file you can choose what language mode to use. I created the example in #100 (comment) in this way, without saving the new file, The extension matching is only for default autoguessing, but you can always choose the language mode of a file from the bottom right bar |
Describe the problem
Similarly to #90 (which is now fixed on the server side), if an ATF file doesn't have atf extension, running validation or lemmatisation on it never returns errors.
I'm not sure how to best address this issue. I see two options:
.atf
extension when trying to do validation/lemmatisation, not having the extension is likely an oversightI guess the decision boils down to whether we want to force the extension in the filename or not
To Reproduce
Create an ATF with this content:
and filename
filename
, without extension. Run validation: the "Validation successful" pop up is always shown, even though there are errors.Expected behavior
Get the "Validation identified errors. See log for details" pop up
Additional context
Like #90, the symptoms are similar to #89.
The text was updated successfully, but these errors were encountered: