MarRue

My feedback

  1. 39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    MarRue supported this idea  · 
  2. 234 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    MarRue supported this idea  · 
  3. 103 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    MarRue commented  · 

    The current documentation (and the api itself) is kind of a mess to be honest. What would be needed to be able to easily work with the api is at least a description of every field that any given get request returns together with its type and whether it is nullable. For example: what the heck are the "ham" and "spam" fields of a tournament supposed to mean?

    MarRue supported this idea  · 
  4. 34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Feature Requests  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    MarRue commented  · 

    This would be a really important feature for developers because as it currently stands, tournament organizers can only do administration tasks via the Challonge website (if the TO hosts the tournament via Challonge), only via the application (if the TO hosts the tournament via the application), the users API key would have to be given to the application, which is, obviously, insecure, or the TO would have to give admin access to the applications user via the website. All of these options are either impractical or insecure, so I would totally love to see that changed.

    MarRue supported this idea  · 

Feedback and Knowledge Base