-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
bug: LfMerge errors not making it to the UI #1303
Comments
C.f. sillsdev/LfMerge#183 |
Yes, this would be a good improvement... |
Some (many?) LfMerge errors are not written with the end user in mind, though. But it might be possible to add some code to LfMerge, and/or the LF code that interacts with LfMerge, to filter error messages and pass through a specific list of error messages that are intended for the end user to see. |
This is actually required for the latest LFMerge changes that are being merged into develop. |
I anticipate that this issue will be fixed once #1444 is implemented. |
Describe the bug
I was recently working with a client who received a generic "Well this is embarrassing..." error during a S/R. I did a little research and finally found the helpful message in the project's
.state
file that looks like it was intended for the end user. I'm not sure where exactly the message got changed when being returned to the user.To Reproduce
The real problem was related to some versioning mismatch between the project on LF and the project on Language Depot.
Expected behavior
I would expect the user to receive the message about the "heritage"
Additional context
My research was on a project that is considered sensitive so additional details of my research are captured in email, just ping me for them.
The text was updated successfully, but these errors were encountered: