Testing the new BingeWorthy w public ratings pages

Open
#45 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
html, javascript
Domain
frontend, testing, web-dev

Research direction

Open http://bingeworthy.io/test.html and verify that the version is 0.5.10, then use the settings gear and Publish tab to enable public ratings. Change ratings and reload the profile page and ratings.json URLs to confirm they update automatically; report whether the flow works or note any errors from the JavaScript console.

Written by the indexing model from the issue text.

Description

The new version is 0.5.10. The test version is here --

http://bingeworthy.io/test.html

There's a lot of new code, but not a lot of new UI. So a careful test that takes about a minute is all it'll take to verify that everything is working as it should.

Make sure the version number says 0.5.10. The previous versions do not have the new features.

You might want to open the JavaScript console to watch for any error messages.

Next to the information icon is a new gear icon for settings. Click it. A settings dialog should appear. There's a single tab entitled Publish.

Check the option to make your ratings public and click the OK button.

You should now have a profile page: http://bingeworthy.io/users/davewiner/ if your screen name is davewiner. There will be a link to this page in the UI but it's not there yet.

Back in BingeWorthy, change some ratings. Then reload the profile page. It should automatically update.

There's also a JSON version of the ratings: http://bingeworthy.io/users/davewiner/ratings.json.

Please let me know if it worked or if there were any problems. Thanks! ;-)

Dave

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.