Right-Click Emote option to put it in the middle of your text
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 45/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
- 领域
- desktop-dev
调研方向
Locate the text input handling and emote processing logic in the Go codebase to implement parsing of :emote_name: patterns and conversion to the internal protocol format like <e:pre:idle:sfx>. Find the emote button UI component to add sequence number highlighting and selected state. Done means mid-text emotes render inline in chat input with sequence numbers displayed on the emote buttons indicating order and count.
由索引模型根据 Issue 内容生成。
描述
Being able to have mid-text emotes properly would be nice. Either right click emote option or typing out the :emote name: like you would a Discord emoji, and placing an emote button in the text to indicate it will swap to it.
I don't want a KFO-Client butchered implementation where it really just sends 2 packets at once (as that HEAVILY relies on the queue actually being enabled to even work properly), I want a proper implementation for it that converts the emote to its own internal variant. For example :emote_name: turns into <e:pre:idle:sfx> or something.
In the same breath, mid-text sfx could also be handled like sfx:sfx_name, etc.
Also add a highlight on the Emote Button in the Emote List when you have mid-emote where the number would show you the order in which they will appear. Additionally if you did an emote twice it would mark it in a way that shows it's being used, for example KC-KZ's idea:
if a emote is high lighted have number 1, 2, 3 and so on with how many are selected in the order you want, if you did the emote twice the emote button would have like "1,3" so at a glance how many times it is used on what order
Also all the emotes that you're using should be using the _on button variant (aka darker shade that they're being used) - on AsyncAO currently that's just a box behind the emote that it's selected so that's what I mean, just mark it as "selected" in addition to the number showing what sequence it's selected in.
Example:
- 主要语言
- Go
- 星标
- 4
- 派生
- 3
- 平均合并
- 6 天 21 小时
- 30 天内合并 PR
- 1
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
SyntaxNyah/AsyncAO 的其他 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 65/100
SyntaxNyah/AsyncAO#156 ·
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
SyntaxNyah/AsyncAO#154 ·
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 68/100
SyntaxNyah/AsyncAO#152 ·
-
good first issue
难度 2/5 1-3 小时 新手友好度 62/100
SyntaxNyah/AsyncAO#107 · 1 条评论 ·
-
enhancement good first issue not before 3.0
难度 2/5 1-3 小时 新手友好度 68/100
SyntaxNyah/AsyncAO#103 ·
查看 SyntaxNyah/AsyncAO 的全部 Issue
相似的 Issue
-
[UI] Add accessible names to Dashboard Workload and HoneyComb dropdowns可能已有人在做 @antcybersec 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
SocialGouv/iterion#3318 ·
维护者通常 1 天内回复
-
area: auth good first issue priority: low type: docs
难度 1/5 1 小时以内 新手友好度 88/100
itadori26/trisse-home#392 ·
维护者通常 1 天内回复
-
good first issue help wanted priority:p2 status:ready type:docs
难度 2/5 1-3 小时 新手友好度 78/100
-
Externe Begrenzung: FNN Steuerbox via GPIO - Abfrage Öffner / Schließer Relais tauschen (invert)未关闭enhancement load management
难度 2/5 1-3 小时 新手友好度 64/100
维护者通常 1 天内回复