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

Automatically create beatmap set description topic on edit if missing #11706

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bdach
Copy link
Contributor

@bdach bdach commented Dec 2, 2024

Note

Please consider this PR as a request for comments / starting point of discussion. It is by no means intended to be 100% complete, and as such I'm opening it as draft until that initial discussion has ran its course and any potential objections have been addressed.

This is a solution to the problem of the new beatmap submission server not creating a description topic for the set like the old one did. Notably, this solution implies several shortcuts:

  • If the main metadata of the set (artist, title) don't change, the forum thread will not be renamed
  • The forum thread will be posted in a hardcoded forum and never moved, while old BSS would move the thread between forums 6 and 10 depending on whether the beatmap is pending or WIP. Not doing this saves a whole bunch of busy work.
  • There is no actual body in the forum thread OP, contrary to what old submission did (example). The 15 dashes are the minimum content that is required to have the existing post parsing logic work.

The aforementioned simplifications were made with the assumption that subforums 6 and 10 on production were going to be hidden away from users due to not containing any actual content that anyone would ever want to see. (Same thing applies to forum 19, which is graveyard - although old threads pre-modding V2 actually do have useful content there. Not sure what to do about that.)

The one and only goal here is that descriptions should be editable for maps submitted using new BSS. Thus I am taking pretty much the same shortcuts that places like the profile page already seem to be.

This is a solution to the problem of the new beatmap submission server
not creating a description topic for the set like the old one did.
Notably, this solution implies several shortcuts:

- If the main metadata of the set (artist, title) don't change, the
  forum thread will not be renamed
- The forum thread will be posted in a hardcoded forum and never moved,
  while old BSS would move the thread between forums 6 and 10 depending
  on whether the beatmap is pending or WIP. Not doing this saves a whole
  bunch of busy work.
- There is no actual body in the forum thread OP, contrary to what old
  submission did.

The aforementioned simplifications were made with the assumption that
subforums 6 and 10 on production were going to be hidden away from users
due to not containing any actual content that anyone would ever want to
see. (Same thing applies to forum 19, which is graveyard.)

The *one and only goal* here is that descriptions should be editable for
maps submitted using new BSS. Thus I am taking pretty much the same
shortcuts that places like the profile page already seem to be.
@nanaya
Copy link
Collaborator

nanaya commented Dec 2, 2024

well this is originally my idea, so 🤷 and yay? 👍

and I think it doesn't have to reuse the existing forum...?

@bdach
Copy link
Contributor Author

bdach commented Dec 2, 2024

Yeah I know you suggested it first. It's moreso that I want as many people as required to agree with this direction. @peppy most of all, probably.

I think it doesn't have to reuse the existing forum...?

It doesn't, sure. The default is set to something that would work on production immediately. Whether a new forum happens for this can be negotiated as one of the details to work out here.

@peppy
Copy link
Member

peppy commented Dec 27, 2024

I have no issue with the direction, FWIW.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants