Tag filter#1879
Conversation
alisa911
left a comment
alisa911
left a comment
There was a problem hiding this comment.
The goal was "one filtering logic". In practice only the predicates (shouldDisplayKey, isKeyToSkip, getPoiAdditionalType) were moved into the shared AdditionalInfoBundle, while the loop that assembles "which tags to show" was duplicated: one copy in SearchService.checkTagsVisibility, a second in Android's AmenityUIHelper.buildInternal, and a third (partial) one in the web fallback fixTagsKeysFallback plus the extra work in groupLocalizedTags. Three sources of truth instead of one.
Move the whole logic into a method in AdditionalInfoBundle. The web should receive a ready to display list of tags, and there should be no groupLocalizedTags or other such logic on the web. The web should only build the UI, which icon, a list or a tag, and so on.
| tagObj.needLinks = false; | ||
| tagObj.textPrefix = value; | ||
| break; | ||
| case OPENING_HOURS: |
There was a problem hiding this comment.
If you touched the switch in buildTagObj, then rewrite it properly
|
This violates map/CLAUDE.md |
There was a problem hiding this comment.
Pull request overview
This PR addresses tag rendering in the OsmAnd Web map “WPT/Favorites” info block by introducing a server-backed visibility filter for tags (related to osmandapp/OsmAnd#24809), and refactoring tag-building to better handle localized variants and POI name tags.
Changes:
- Add a
/search/get-tags-visibilityPOST call to filter/normalize tag visibility before rendering. - Refactor tag construction into helpers (
buildTagObj, grouping localized tags, handling POI name + other languages). - Add client-side filtering of certain web-only/internal keys before visibility processing.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
osmandapp/OsmAnd#24809