I have taken a look at your code and the link wouldn't work if the builder update was merged. I will change the builder to make it copy folders inside of the static folder into the documents folder so that you don't have to update your code in any way.

As other input options will appear, you might want to change radio button by select if it is within the design proposal, it would look like this:

https://user-images.githubusercontent.com/30236552/122628286-a7d94e00-d08b-11eb-8b72-3636f4758ac7.mp4

I started to think of a way to add the textarea I managed to get a result but I don't know if it is the path they would like to follow.

When I add the textarea to get for line breaks I only stop at the last occurrence of \n but this breaks the input test.

Is allowing line breaks in an input really a problem? if yes, how can we get around ?

to IO.gets work with textarea I made the adjustment below in the file io_proxy.ex

  defp line_from_input(input) do
    case :binary.match(input, ["\r\n", "\n"]) do
      :nomatch ->
        {input, ""}

      {pos, len} ->
        size = byte_size(input)
        line = binary_part(input, 0, pos + len)
        rest = binary_part(input, pos + len, size - pos - len)

        {line_tail, rest_tail} = line_from_input(rest)
        {line <> line_tail, rest_tail}

    end
  end

@saranshgrover this did indeed cause an issue. The way the builder works right now is it creates temporary PDFs in the documents folder, copies them into build and then deletes all PDFs in documents. I have changed the builder here and moved the finance documents to a new "static" folder. All pre-rendered PDFs should be stored here; the builder copies them at the end, so they will be found in build/static/finances.

LGTM (although I'm not a WST member :P

I feel like we should wait until all of the most important pages have been migrated to React and then use the fomantic UI to set dark mode

Addresses issue https://github.com/thewca/worldcubeassociation.org/issues/4673. This simply sets the default to registration emails for delegates and organizers to false, so that they can opt in to receiving these emails if they so choose. Please review that I implemented the change correctly.

This conversation actually got me thinking about why the WCA even needs to store gender information. It's not like speedcubing is an athletic sport where there's an unfair advantage towards any gender.

I listed a couple reasons 2 messages above. Another is we now have gender rankings on the website.

Oh, I'm sorry. I didn't realize we even had those rankings. I think male, female and other should be fine. Maybe we can email the competitors with "other" and ask for their opinion?

Not that this matters, but Since the start of 2019, a majority of people have had this checkbox checked (but that might just be due to it being the default option):

So I wouldn't change the default, but I definitely think it should be moved to a user preferences page.

I'm almost certain that's why

This conversation actually got me thinking about why the WCA even needs to store gender information. It's not like speedcubing is an athletic sport where there's an unfair advantage towards any gender.

I listed a couple reasons 2 messages above. Another is we now have gender rankings on the website.

I don't see this as useful personally. I just bookmark comps to make sure I get an email when the registration opens.

This conversation actually got me thinking about why the WCA even needs to store gender information. It's not like speedcubing is an athletic sport where there's an unfair advantage towards any gender.

@denthebro to be clear - are you working on porting this to React, or simply porting it to Formantic UI?

Well, both. I am making a React component with the use of Fomantic UI. Here's an image of my current WIP: https://imgur.com/3Vz7zI0

I agree with @Jambrose777

Fixes #4984 where the default was changed in #4198

@Jambrose777 you're right, competition by competition would be good functionality - although we already have that in that Delegates can forward on an invoice (but are still responsible for paying it). However making it competition-by-competition would add extra steps for the people who are always in one category (about 1/3 of delegates). Currently those delegates don't have to do anything as it is captured in a spreadsheet the WFC maintains - this is really just shifting existing functionality to the website and making it user editable.

Gotchya, so both ideas can be implemented to cover both cases :) (I hadn't realized WFC was already doing this as a manual process with spreadsheets)

@Jambrose777 you're right, competition by competition would be good functionality - although we already have that in that Delegates can forward on an invoice (but are still responsible for paying it). However making it competition-by-competition would add extra steps for the people who are always in one category (about 1/3 of delegates). Currently those delegates don't have to do anything as it is captured in a spreadsheet the WFC maintains - this is really just shifting existing functionality to the website and making it user editable.

Marked as low priority, since it is no longer the homepage and we removed the two biggest categories for this. But We do already have tags for posts (which I believe are fully utilized for all posts already?) so it would just be creating a dropdown menu to filter on those tags. A user is also able to use the main search feature to find all posts of a certain type. Still a good easy first issue for anyone wanting to do it!

See poll: https://forum.worldcubeassociation.org/t/competition-schedule-default-view/14287

I personally prefer the Calendar view and always have to change it.

Just a note: Would it be better for this to be on the competition level and not the user level?

Ie. I may have the following comps:

• Comp 1, where I want the dues sent to me, the Delegate
• Comp 2, where I was a supporting Delegate and the dues should be sent to the Main Delegate who handled finances.
• Comp 3, where the organizer handled finances
• Comp 4, where a regional organization handles finances.

You're suggestion would imply that I as a Delegate would always fall into 1 of the 4 categories, where it is often the case that it may be different per competition.

For those tracking this issue, #423 uses a new version of TensorFlow which should support Mac ARM. I believe you might need Bazel 4.1. If anybody would like to take a shot at building off of that branch, that would be really appreciated

Is this still an issue? Admittedly, I'm too scared to try it with my own comps :P

Might be kind of difficult, but would definitely be a nice to have! I've always accomplished this with Themes on projects I worked on, but those themes were also used to change looks quite often, so it would be overkill here maybe?

Marked as high priority as this was a feature that we lost with Cubecomps being deprecated, and the manual process for Delegates is quite tedious as Tim mentioned.

Right now Delegates/Organizers can select events format that are no longer recognized on the Regulations while editing a competition. This should be updated so you can only select recognized formats by the Regulations (see regulation 9b).

Closing in favor of #3752

Can WFC (Cc: @Mollerz) give a bit of explanation of what they would want this to look like / the different parts this impacts.

It looks like whoever picks this up will need to study #4709 for how country bands are used.

Closing this as expected behavior. We also give a warning/error before the competition is announced and we have an open issue for after its announced: #4653

Describe the bug When I remove an event or round, it is still visible in the "Manage schedule" page

To Reproduce Steps to reproduce the behavior:

1. Go to a competition you can manage
2. Add some events and add all rounds to the schedule
3. Go to "Manage events" and remove an event or remove a round
4. Go to "Manage schedule". The removed round(s) are still there

Expected behavior In step 4, I expect the removed round(s) to be removed

Desktop (please complete the following information):

• OS: Windows
• Browser: Chrome