Revamp scores

[RyanTG]

Working currently ongoing. pinballmap/pbm#1692

• Show highest score list on profile
• other stuff that I'll add...

Documenting API changes:

/api/v1/location_machine_xrefs/:id.json
?user_id=0 when not logged in and ?user_id=actual id when logged in

if logged in and has score, then also include:
/api/v1/machine_score_xrefs/high.json?by_machine_id=xx;by_user_id=xx

/api/v1/user_submissions/location.json
/api/v1/user_submissions/list_within_range.json
user_id
restrict_to

Example: http://localhost:3000/api/v1/user_submissions/location.json?id=16910;user_id=2;restrict_to=new_msx;submission_type[]=add_location;submission_type[]=new_lmx;submission_type[]=remove_machine;submission_type[]=new_condition;submission_type[]=confirm_location;submission_type[]=new_msx

/api/v1/users/:id/profile_info.json
new_score_list_only
"profile_list_of_high_scores"

[RyanTG]

Additional things that should be done:

• locationDetails includes a no_details endpoint flag that excludes comments and scores. Comments and scores requested with location_machine_xrefs endpoint when machine name is clicked.

Details:

Right now the locations endpoint returns machines, comments, and scores.

We are changing machineDetails so that other people's scores are not included. There should be one API request for locationDetails, and another for machineDetails.

locationDetails request: /api/v1/locations/:id.json?no_details=1

machineDetails request:

loggedIn ? /api/v1/location_machine_xrefs/:id.json?user_id=${userId}

:id is the LMX id. The ID param does not affect comments; only scores.

NOT loggedIn ? /api/v1/location_machine_xrefs/:id.json?user_id=0

The 0 excludes scores. On the website we're going to hide all scores from logged out users, so we'll do the same here. If we decide to change it, then we'll change it.

• recent and location activity filtering is not applied until the apply button is clicked, and does a new query.

Details:

Right now with the activity feeds, we pull 200 items, and then filter on those 200 items. Instead we should make a fresh request when filtering, so that there is always the potential for 200 items.

First off, these feeds will now hide scores from other users. Two new params to use:

loggedIn ? user_id=$(userId};restrict_to=new_msx

NOT loggedIn ? restrict_to=new_msx

Then, the two endpoints accept query strings for the submission types. But they are not required. If not included, they default to the full list that we include.

So, query strings are only needed if actually filtering - if not filtering, then no query strings needed.

/api/v1/user_submissions/location.json
/api/v1/user_submissions/list_within_range.json

Example of all the query strings for submission types, with the new user_id and restrict_to included:

/api/v1/user_submissions/location.json?id=${location_id};user_id=${userId};restrict_to=new_msx;submission_type[]=add_location;submission_type[]=new_lmx;submission_type[]=remove_machine;submission_type[]=new_condition;submission_type[]=confirm_location;submission_type[]=new_msx