Commit 0dd7e228 authored by Mikaël Salson's avatar Mikaël Salson Seems that safe_encoding is no more needed now

See #3097

Discussed with @magiraud and @RyanHerb: The UTF-8 is now properly handled when
processing JSON. An example of that is that runs and sets don't need safe_encoding.

However there is still a small issue (that pre-existed): in anon mode, the three
first bytes are recovered which may not correspond to a valid character.
parent bd786b7e
Pipeline #20011 passed with stages
in 19 seconds
......@@ -104,12 +104,11 @@ def anon_names(sample_set_id, first_name, last_name, can_view=None):
ln = safe_encoding(last_name)
fn = safe_encoding(first_name)
ln = last_name
fn = first_name
if can_view or (can_view == None and auth.can_view_info('sample_set', sample_set_id)):
name = ln + " " + fn
ln = safe_encoding(last_name)
name = ln[:3]
return name
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment