EZP-31248: Fixed handling non-printable characters for Search#2904
EZP-31248: Fixed handling non-printable characters for Search#2904alongosz merged 10 commits intoezsystems:7.5from
Conversation
|
@kmadejski is this overlapping with the PR you proposed perhaps? |
|
@hgiesenow thanks for your contribution! @andrerom yes, it seems to cover also what I've tried to achieve in my PR. This is also probably what @gggeek had in mind in ezsystems/ezplatform-solr-search-engine#159 (comment). @hgiesenow could you please double-check whether it for sure covers what has been described in this ticket: https://jira.ez.no/browse/EZP-30759? |
|
Maybe :-) I don't remember the details. Otoh I think that some of the chars that are trimmed-away at the moment (both before and with this PR) should not be replaced with no-char but with a space instead. Esp. tab, vertical-tab, form-feed could conceivably be used to separate two words. If we strip them out, we'd be joining those words together... possibly chars 1C-1E as well |
|
Hi @hgiesenow, do you need any help with this PR? 🙂 |
|
Hi @kmadejski, @gggeek - I pushed a commit that handles tabs, horizontal tabs and form feed, so they are replaced with space. Can you please give your review (for some reason I can't add you to reviewers)? |
|
better :-) |
eZ/Publish/Core/Search/Common/FieldValueMapper/StringMapper.php
Outdated
Show resolved
Hide resolved
|
@adamwojs had some problems with those, but should be ok now 😉 |
Co-Authored-By: Andrew Longosz <alongosz@users.noreply.github.com>
Co-Authored-By: Andrew Longosz <alongosz@users.noreply.github.com>
Co-Authored-By: Andrew Longosz <alongosz@users.noreply.github.com>
tomaszszopinski
left a comment
There was a problem hiding this comment.
QA approved on eZ Platform EE 2.5 with diff.
|
Merged for eZ Platform Thank you @hgiesenow and @mateuszbieniek 🎉 |
7.xReplaces all special chracaters to avoid issues with SolR
TODO:
$ composer fix-cs).