-
Notifications
You must be signed in to change notification settings - Fork 25
Change ages indexation approach #133
Comments
@KylieAldridge for the Jira |
Jira ticket: https://openy.atlassian.net/browse/PRODDEV-515 |
merged, this one should be fixed now @duozersk is there any test we can use for QA? |
Well... testing it is quite cumbersome. We should have the session/activity (either in demo content or create manually) with the min age set to smth that is not dividable by 6 (in months). Like from min age 15 months to max age 36 months. The code before the fix would index 15, 21, 27 and 33 months into the search index for this activity and this session wouldn't be there in the results for any of the age filters (as the ages configuration doesn't have these numbers). The new version of code would index 18, 24 and 36 months - based on the ages configuration - and the activity will be there in the results in you select appropriate age filter. Ages configuration is this one - https://github.com/ymcatwincities/openy_activity_finder/blob/4.x/config/install/openy_activity_finder.settings.yml#L4 |
I installed
Once I updated to |
Yes, we need to tag a new release @froboy |
Currently we are indexing from min age to max age with the 6 months steps.
https://github.com/ymcatwincities/openy_activity_finder/blob/4.x/src/Plugin/search_api/processor/AgesMinMax.php#L67
It has several flaws:
The text was updated successfully, but these errors were encountered: