We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Heeeeey @Joxit I was investigating a bug report today and I noticed something on our dev server which looks incorrect: https://pelias.github.io/compare/#/v1/autocomplete?lang=de&text=Am+Gro%C3%9Fhausberg%2C+Furtwangen+im+Schwarzwald+deut&debug=1 Dev server is running a newer master branch than the production server. The screenshot shows it's using phrase.default but name.de, is that possibly due to this PR? I would expect to see phrase.default and phrase.de.
Heeeeey @Joxit
I was investigating a bug report today and I noticed something on our dev server which looks incorrect: https://pelias.github.io/compare/#/v1/autocomplete?lang=de&text=Am+Gro%C3%9Fhausberg%2C+Furtwangen+im+Schwarzwald+deut&debug=1
Dev server is running a newer master branch than the production server.
master
The screenshot shows it's using phrase.default but name.de, is that possibly due to this PR? I would expect to see phrase.default and phrase.de.
phrase.default
name.de
phrase.de
Originally posted by @missinglink in #1493 (comment)
Expected behavior
We should use the phrase.{lang} field instead of name.{lang}.
phrase.{lang}
name.{lang}
Additional context
Here is where we update the name.default field to phrase.default:
name.default
api/query/view/admin_multi_match_first.js
Lines 32 to 37 in 5d202c4
The lang from clean is not available in this function... We may add a new property lang in the view ?
clean
lang
The text was updated successfully, but these errors were encountered:
admin_multi_match_first
Joxit
Successfully merging a pull request may close this issue.
Describe the bug
Originally posted by @missinglink in #1493 (comment)
Expected behavior
We should use the
phrase.{lang}
field instead ofname.{lang}
.Additional context
Here is where we update the
name.default
field tophrase.default
:api/query/view/admin_multi_match_first.js
Lines 32 to 37 in 5d202c4
The lang from
clean
is not available in this function... We may add a new propertylang
in the view ?The text was updated successfully, but these errors were encountered: