#Make /tags entries clickable #866 contribution.

1 messages · Page 1 of 1 (latest)

lofty wave
#

Hello, I have been coding with java for a year and I want to start to contribute to open source projects. I found this issue on GitHub and I would like to start working on it. Can I ?

sweet cosmosBOT
#

<@&987246924425994290> please have a look, thanks.

sweet cosmosBOT
#

While you are waiting for getting help, here are some tips to improve your experience:

Code is much easier to read if posted with syntax highlighting and proper formatting.

If nobody is calling back, that usually means that your question was not well asked and hence nobody feels confident enough answering. Try to use your time to elaborate, provide details, context, more code, examples and maybe some screenshots. With enough info, someone knows the answer for sure.

Don't forget to close your thread using the command </help-thread close:1027500463647621170> when your question has been answered, thanks.

marble loom
#

@lofty wave Hi, you're more than welcome to join our community project. Please do mention on the issue, so that you can be assigned to it. Feel free to post any questions/ideas or doubts you have there😄

lofty wave
#

Fine, thank you. However I am not exactly sure if I understand what is the problem. Could you briefly explain me please ? 😅

#

Do I understand it correctly, that if there is written "/tags" anywhere in a message it should be clickable and put into the message box ?

alpine scroll
#

btw, we can discuss this on github directly

#

in the issue

marble loom
#

ye that's better to keep record of suggestions and ideas

alpine scroll
#

ill add some details to the issue

lofty wave
lofty wave
alpine scroll
#

slash commands can be made "clickable"

#

this requires a special syntax

#

when u use /tags, everything is plain text

sweet cosmosBOT
#
All available tags

• ++
• abstract
• abstract-interface
• adoptium
• ask
• ask-long
• bfs
• busy
• code
• dfs
• doesntwork
• double
• equals
• executable-Jar
• executors
• float
• format
• gsdp
• homework
• ide
• install
• instance
• interface
• interrupt
• jarfix
• javafx-swing
• jpackage
• js
• lobby
• lsp
• mcve
• mooc
• mre
• naming
• nio
• only-nio
• operators
• parseLine
• person
• ping
• projects
• regex
• scanner
• share
• static
• this
• tutorials
• uri
• version
• visibility
• xy

zabuzard • used /tags ·
alpine scroll
#

the idea is that all of those are made to clickables

#

we have an utility method for getting a clickable slash command text

#

so u just have to use that utility method correctly

#

the string u get back has the format </123:foo bar> with 123 being the id of the command and foo bar being the subcommand text

lofty wave
#

And when I click on them should they be moved to the message box ?

alpine scroll
#

but thats just discord syntax

#

u dont have do do anything for that

#

see, ill show u

#

the /tags command has id 911187149125206033

#

so if u write the magic text </911187149125206033:xy>, the following happens: </911187149125206033:xy>

#

lmao, fail

lofty wave
#

xD

alpine scroll
#

well, perhaps only a bot can post it

#

but the thing is, the magical text is

#

</tags xy:911187149125206033>

#

and then, when the bot posts that

#

it turns into a clickable command

#

so instead of writing

All available tags:
* xy
* mooc
...
#

u would write

# 
All available tags:
* </tags xy:911187149125206033>
* </tags mooc:911187149125206033>
...
lofty wave
#

Fine, thank you. I understand much more now, I will write a message to the issue on GitHub and start to work on it 😁

alpine scroll
#

its just that u must not hardcode this ID, cause it changes. it has to be retrieved dynamically. which is what our utility method mentionGuildSlashCommand does