You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user should be able to use /user command with optional arguments. Optional arguments to be added are
GitHub
LinkedIn
Twitter
Instagram
Expected Behavior
When a user uses /user command on chat, it should show the above four new optional argument fields. If given 'show' value to those arguments, the response should include the user's respective social media details.
Current Behavior
Upon using /user command it shows 'username' field as a mandatory argument and 'dev' as an optional argument.
Screenshots
Reproducibility
This issue is reproducible
This issue is not reproducible
Steps to Reproduce
Run /user command on chat
Severity/Priority
Critical
High
Medium
Low
Additional Information
Checklist
I have read and followed the project's code of conduct.
I have searched for similar issues before creating this one.
I have provided all the necessary information to understand and reproduce the issue.
I am willing to contribute to the resolution of this issue.
The text was updated successfully, but these errors were encountered:
nisargmakwana
changed the title
Allow optional arguments to search a user using /user command
Allow optional arguments for social media details on /user command
Sep 18, 2024
Issue Description
A user should be able to use /user command with optional arguments. Optional arguments to be added are
Expected Behavior
When a user uses /user command on chat, it should show the above four new optional argument fields. If given 'show' value to those arguments, the response should include the user's respective social media details.
Current Behavior
Upon using /user command it shows 'username' field as a mandatory argument and 'dev' as an optional argument.
Screenshots
Reproducibility
Steps to Reproduce
Severity/Priority
Additional Information
Checklist
The text was updated successfully, but these errors were encountered: