Skip to content
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.

The matching attributes are not always the one we retrieve or display #172

Closed
redox opened this issue May 30, 2016 · 2 comments
Closed

The matching attributes are not always the one we retrieve or display #172

redox opened this issue May 30, 2016 · 2 comments
Assignees

Comments

@redox
Copy link
Contributor

redox commented May 30, 2016

Another language is matching:

screen shot 2016-05-31 at 12 23 58

The locale_name is multi-valued, and we only display city[0]

screen shot 2016-05-31 at 12 24 43

@redox redox changed the title We need to select the matching locale_name The matching attributes are not always the one we retrieve or display May 31, 2016
@vvo
Copy link
Contributor

vvo commented Jun 20, 2016

Unsure what we need to do here exactly

@redox
Copy link
Contributor Author

redox commented Jun 20, 2016

Unsure what we need to do here exactly

Some of the underlying attributes are multi-valued but we always use [0] for the displayed value. We need to somehow iterate over the _highlightResult to add other matching strings.

For Paris, it looks like:

locale_names: ["Paris", "Lutèce"]

So, for the lutec query I probably expect something like:

Paris (**Lutec**e), Ile-de-France, France

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants