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

[bug] Report Category always shows as "other" #2679

Open
moan0s opened this issue Feb 22, 2024 · 2 comments
Open

[bug] Report Category always shows as "other" #2679

moan0s opened this issue Feb 22, 2024 · 2 comments
Labels
bug Something isn't working not implemented yet We probably will implement this. But we haven't yet ;)

Comments

@moan0s
Copy link
Contributor

moan0s commented Feb 22, 2024

Describe the bug with a clear and concise description of what the bug is.

When a post is reported for breach of a specific server rule this rule is not shown in the admin interface.

What's your GoToSocial Version?

v0.13.3 git-fb3e3ca

GoToSocial Arch

docker x86_64

What happened?

see steps to reproduce

What you expected to happen?

I expect to be shown the rule that was breached.

How to reproduce it?

  • Set some server rules in the GTS admin interface
  • Report a post for breach of a specific server rule
  • Check the report section of the admin interface
  • See Category: other shown

Anything else we need to know?

Tested with elk.zone by me and a development version of phanpy.social by Chee Aun. Semaphore and Tusky don't seem to be able to report specific server rules.

@moan0s moan0s added the bug Something isn't working label Feb 22, 2024
@tsmethurst
Copy link
Contributor

Oh thanks. Not a bug really, it's just not implemented yet :P

@tsmethurst tsmethurst added the not implemented yet We probably will implement this. But we haven't yet ;) label Feb 22, 2024
@moan0s
Copy link
Contributor Author

moan0s commented Feb 22, 2024

Okay, thanks for clarifying! I was pleasantly surprised that server rules were implemented at least partially and I'll happily wait for other features :)

Edit: I also checked the database with SELECT created_at, account_id, comment, rules FROM reports; which confirmed that the rule that was broken is already recorded (and helped test the phanpy implementation).
A bit more in depth

 SELECT
      r.created_at,
      a.username,
      r.comment,
      r.rules,
      ru.text AS rule_text,
      ru.id AS id
FROM reports r
CROSS JOIN LATERAL unnest(r.rules) AS rule_id
JOIN rules ru ON ru.id = rule_id
JOIN accounts a ON r.account_id = a.id;

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working not implemented yet We probably will implement this. But we haven't yet ;)
Projects
None yet
Development

No branches or pull requests

2 participants