Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reference to the Codidactyl in non-Codidact instances #1396

Open
trichoplax opened this issue Sep 8, 2024 · 1 comment
Open

Reference to the Codidactyl in non-Codidact instances #1396

trichoplax opened this issue Sep 8, 2024 · 1 comment
Labels
area: ruby Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: bug Something isn't working

Comments

@trichoplax
Copy link
Contributor

Describe the bug
When viewing the user page for a deleted user, the following message is displayed, which may be confusing for a user of an instance other than Codidact:

User accounts make an excellent snack for the Codidactyl.

To Reproduce
Steps to reproduce the behavior:

  1. Create a user account in a development environment.
  2. Delete the user, making a note of their user id.
  3. View your own user page.
  4. Change the URL to use the deleted user's user id instead of your own.
  5. See a deleted user message, including the message mentioning the Codidactyl.

Expected behavior
Hardcoded messages should be suitable for all instances, not just Codidact. Anything that only applies to Codidact should be conditional, so that it only appears when viewed from the Codidact instance.

Personally, I would also question whether we should have in-jokes at all in the user interface as the Codidact communities grow, as new users will have no context.

@cellio
Copy link
Member

cellio commented Sep 8, 2024

Agreed this should be configuration or generic. It's fine to have a "mascot" that shows up in passing, and maybe we should have a "what is the Codidactyl?" help page that we can link to from such mentions, but if it gets in the way of comprehension, we should adjust. I love the Codidactyl, but we want it to be friendly, not befuddling.

Changing this particular string is easy, but I tagged it as complexity:unassessed because I don't know about other hard-coded strings. If we focus this issue on just the user page, this should be a one-liner.

@cellio cellio added area: ruby Changes to server-side code type: bug Something isn't working priority: medium complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. labels Sep 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ruby Changes to server-side code complexity: unassessed Needs further developer investigation before complexity/feasibility can be determined. priority: medium type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants