When using the views_json_source module to query JSON APIs, I encountered an issue with string matching when the strings contain accented or special characters. For example, a search for "prévoyance" does not return results if the string in the JSON is "prevoyance". This is due to the lack of transliteration handling in string comparisons, which prevents matching similar strings with different accents or special characters.
1. Use the views_json_source module to query a JSON API.
2. Ensure the JSON data contains strings with accented or special characters (e.g., "prevoyance").
3. Perform a search using a string with different accents or special characters (e.g., "prévoyance").
4. Observe that the search does not return the expected results due to the lack of transliteration handling.
To address this issue, I added transliteration handling to the views_json_source module. The following changes were made:
Modification of the ViewsJsonQuery class to handle transliteration:
- Added a transliterateValue method to transliterate values before comparing them.
- Modified the ops method to use transliteration during string comparisons.
- Review the changes to ensure they meet the module's standards.
- Test the changes in various scenarios to confirm that transliteration handling works as expected.
- Update the documentation to reflect the new transliteration handling feature.
No user interface changes are required. The transliteration handling is automatically applied during string comparisons in JSON queries.
No API changes are required. The transliteration handling is integrated into the existing methods of the ViewsJsonQuery class.
No data model changes are required. The transliteration handling does not affect the data structure or storage.
Downport
2.0
Code
astonvictor → changed the visibility of the branch 2.0.x to hidden.
Automatically closed - issue fixed for 2 weeks with no activity.