1617aa2756
If we put the emoji filter before the reference filters, each emoji will
have a wrapper element that prevents the reference filter from detecting
the presence of the emoji.
As the emoji filter now runs after the reference filters, references
must contain a literal emoji, not the GitLab Flavored Markdown
versions (:100`, for example).
A weird side-effect is that if you have a label with the 100 emoji, and
a label named 💯, then trying to reference the latter will work (link
to the correct label), but will render with the 100 emoji. I'm
comfortable with that edge case, I think.
|
||
|---|---|---|
| .. | ||
| api | ||
| assets | ||
| backup | ||
| banzai | ||
| bitbucket | ||
| bitbucket_server | ||
| constraints | ||
| container_registry | ||
| declarative_policy | ||
| flowdock | ||
| generators/rails/post_deployment_migration | ||
| gitaly | ||
| gitlab | ||
| google_api | ||
| json_web_token | ||
| mattermost | ||
| microsoft_teams | ||
| object_storage | ||
| omni_auth/strategies | ||
| peek | ||
| quality | ||
| rouge | ||
| rspec_flaky | ||
| safe_zip | ||
| sentry | ||
| serializers | ||
| support | ||
| system_check | ||
| tasks | ||
| after_commit_queue.rb | ||
| backup.rb | ||
| banzai.rb | ||
| carrier_wave_string_file.rb | ||
| declarative_policy.rb | ||
| event_filter.rb | ||
| expand_variables.rb | ||
| extracts_path.rb | ||
| feature.rb | ||
| file_size_validator.rb | ||
| forever.rb | ||
| gitlab.rb | ||
| gt_one_coercion.rb | ||
| milestone_array.rb | ||
| mysql_zero_date.rb | ||
| static_model.rb | ||
| system_check.rb | ||
| uploaded_file.rb | ||
| version_check.rb | ||