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.

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

feat(magnifying glass): use the magnifying glass to find the first choice to see on the map #1600

Open
wants to merge 13 commits into
base: release/16.x
Choose a base branch
from

Conversation

MSPKarengeo
Copy link
Contributor

Please check if the PR fulfills these requirements

What is the current behavior? (You can also link to an open issue here)
N/A

What is the new behavior?
The magnifying glass will find the first score that best matches the search to view it on the map

Does this PR introduce a breaking change? (check one with "x")

  • Yes
  • No

If this PR contains a breaking change, please describe the impact and migration path for existing applications:
N/A

Other information:

@MSPKarengeo MSPKarengeo added the enhancement New features and improvements // Nouvelles fonctionnalités et améliorations label Jan 25, 2024
@alecarn
Copy link
Collaborator

alecarn commented Feb 5, 2024

Pourrais-tu nous indiquer comment qu'on peut tester les changements?

R: Pour faire marcher la loupe, il faut activer à true dans ces deux lignes du fichier search-bar.component.ts :
https://vscode.dev/github/infra-geo-ouverte/igo2-lib/blob/nv_search_first_element_by_magnifying_glass/packages/geo/src/lib/search/search-bar/search-bar.component.ts#L288

this.showSearchButton = configValue !== undefined ? configValue : false; à true

https://vscode.dev/github/infra-geo-ouverte/igo2-lib/blob/nv_search_first_element_by_magnifying_glass/packages/geo/src/lib/search/search-bar/search-bar.component.ts#L88
public showSearchButton: boolean = false; à true

@alecarn alecarn mentioned this pull request Feb 6, 2024
5 tasks
@MSPKarengeo
Copy link
Contributor Author

Corrections et modifications on été effectuées. Disponibles pour révision.

@alecarn alecarn changed the base branch from next to release/16.x February 29, 2024 18:18
Copy link
Collaborator

@alecarn alecarn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deux questionnements sinon ça me semble beau 👍

@alecarn alecarn requested a review from pelord March 11, 2024 20:00
@alecarn
Copy link
Collaborator

alecarn commented Mar 11, 2024

@pelord ready for your review

Copy link
Member

@pelord pelord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

J'ai cette erreur.

image

@alecarn alecarn self-requested a review March 28, 2024 17:16
@alecarn alecarn assigned aziz-access and unassigned MSPKarengeo Nov 14, 2024
@aziz-access aziz-access force-pushed the nv_search_first_element_by_magnifying_glass branch from 8b4451e to 10db31b Compare November 14, 2024 16:04
@aziz-access
Copy link
Contributor

aziz-access commented Nov 19, 2024

J'ai cette erreur.

image

modifier l'option showSearchButton true dans config.json

 "searchBar": {
    "showSearchBar": true,
    "showSearchButton": true
  },

Il faut ajouter l'input map dans le composant <igo-search-bar> portal component (igo2).
image

@aziz-access aziz-access requested a review from pelord November 19, 2024 16:02
@alecarn alecarn force-pushed the nv_search_first_element_by_magnifying_glass branch from 25a67af to 745f5cf Compare November 26, 2024 15:22
@alecarn
Copy link
Collaborator

alecarn commented Nov 26, 2024

@pelord, ready for review/test

@alecarn alecarn force-pushed the nv_search_first_element_by_magnifying_glass branch from 745f5cf to 754da18 Compare November 26, 2024 15:29
@pelord
Copy link
Member

pelord commented Dec 4, 2024

pourquoi pas pousser dans next?

Copy link
Member

@pelord pelord left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarifier comment gérer les resultats asynchrone? Les services qui sont plus lent? P-etre tester avec un debouncetime random entre 500 et 2000 ms?

* When the user clicks on the magnifying glass and
* this find the first object on the map
*/
selectFirstElement() {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qu'est-ce qui arrive si les résultats ne sont pas tous arrivés lorsque l'utilisateur clique le bouton?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rien ne s'est passé, s'il y a un résultat, le résultat avec le score le plus élevé sera mis en évidence

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mais disons q'un utilisateur clique sur le boutin ou fait enter, mais que seul des résultats partiels sont disponible?

Quelle est l'échelle relative comparable entre les résultats? Comment comparer des résultats? Regarde computeTermSimilarity

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

chaque résultat a un score donc en utilise le score pour la comparaison

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Le score est-il comparable entre les services de recherche?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

il faudrait idéalement que ce soit sur une échelle absolue et non pas relative, comme pour iCherche

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

le code existant bien tester avec iCherche, le résultats de recherche donne le même objet, donc le score existe si le résultat est une couche ou Feature.
existe-t-il un autre service où je peux tester?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nominatim?

@@ -15,28 +15,33 @@
: undefined
"
[value]="term$ | async"
(keydown.enter)="selectFirstElement()"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Est-ce que le keydown.enter ne devrait pas re-trigger la recherche également?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • sélectionner le 1er résultat?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oui sélectionner le résultat avec le score le plus élevé

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Je crois que enter devrait redéclancher la recherche.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting response enhancement New features and improvements // Nouvelles fonctionnalités et améliorations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Recherche - Ajout de la loupe dans la barre de recherche (optionnel)
5 participants