Edit history

Earlier versions of Typing @@ shows `@everyone` and `@here`, newest first.

Current version | Edited by Rex
Changes
2. Observe all mentions apart from `@everyone` and `@here` disappearing.Removed: ### EnvironmentRemoved: Removed: _No response_Removed: Removed: ### Logs or screenshotsRemoved: Removed: _No response_Removed: Removed: ### ChecksRemoved: Removed: - ☑ I searched existing issues.Removed: - ☑ I wrote this report in my own words, except for direct translation if needed.Removed:
Show

Typing @@ shows `@everyone` and `@here`

Summary

(originally reported in #440; still happening) Typing @@ shows @everyone and @here in the autocomplete despite them not containing the substring @@. This is inconsistent with the roles which do not show up Some people like to end their messages with ^^ and if they accidentally type @@ (note: I am unsure how exactly this happens but I witnessed it in a fairly large server) and press enter instead that's a recipe for disaster The simplest fix would probably be to add substring(1) here: https://github.com/fluxerapp/fluxer/blob/refactor/fluxer_app/src/hooks/useTextareaAutocomplete.tsx#L802
return mention.kind.substring(1).toLowerCase().includes(queryForMatching.toLowerCase());
or add @ to the query
return mention.kind.toLowerCase().includes("@" + queryForMatching.toLowerCase());

Steps to reproduce

  1. Type @ twice the chatbox.
  2. Observe all mentions apart from @everyone and @here disappearing.
Edited by Rex
Changes
Removed: Typing @@ shows @everyone and @hereAdded: Typing @@ shows `@everyone` and `@here`### SummaryRemoved: (originally reported in [#737](https://feedback.fluxer.com/p/440); still happening)Added: (originally reported in [#440](https://feedback.fluxer.com/p/440); still happening)Typing @@ shows `@everyone` and `@here` in the autocomplete despite them not containing the substring `@@`. This is inconsistent with the roles which do not show up
Show

Typing @@ shows `@everyone` and `@here`

Summary

(originally reported in #440; still happening) Typing @@ shows @everyone and @here in the autocomplete despite them not containing the substring @@. This is inconsistent with the roles which do not show up Some people like to end their messages with ^^ and if they accidentally type @@ (note: I am unsure how exactly this happens but I witnessed it in a fairly large server) and press enter instead that's a recipe for disaster The simplest fix would probably be to add substring(1) here: https://github.com/fluxerapp/fluxer/blob/refactor/fluxer_app/src/hooks/useTextareaAutocomplete.tsx#L802
return mention.kind.substring(1).toLowerCase().includes(queryForMatching.toLowerCase());
or add @ to the query
return mention.kind.toLowerCase().includes("@" + queryForMatching.toLowerCase());

Steps to reproduce

  1. Type @ twice the chatbox.
  2. Observe all mentions apart from @everyone and @here disappearing.

Environment

No response

Logs or screenshots

No response

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.
Original by Rex
Show

Typing @@ shows @everyone and @here

Summary

(originally reported in #737; still happening) Typing @@ shows @everyone and @here in the autocomplete despite them not containing the substring @@. This is inconsistent with the roles which do not show up Some people like to end their messages with ^^ and if they accidentally type @@ (note: I am unsure how exactly this happens but I witnessed it in a fairly large server) and press enter instead that's a recipe for disaster The simplest fix would probably be to add substring(1) here: https://github.com/fluxerapp/fluxer/blob/refactor/fluxer_app/src/hooks/useTextareaAutocomplete.tsx#L802
return mention.kind.substring(1).toLowerCase().includes(queryForMatching.toLowerCase());
or add @ to the query
return mention.kind.toLowerCase().includes("@" + queryForMatching.toLowerCase());

Steps to reproduce

  1. Type @ twice the chatbox.
  2. Observe all mentions apart from @everyone and @here disappearing.

Environment

No response

Logs or screenshots

No response

Checks

  • ☑ I searched existing issues.
  • ☑ I wrote this report in my own words, except for direct translation if needed.