This will probably require pg-search.

Right now the <genre-select> component just does a really ignorant thing where it gets the whole genre index and then filters locally. This isn't feasible for something like the developer or publisher fields.

Users should have usernames (and display names?)

Wikidata has some data that they've used to import video game info: https://tools.wmflabs.org/mix-n-match/#/group/ig_video_games

You can actually download each of these in their full JSON format, a complete log of every game on, e.g. GiantBomb. Also useful for game platforms.

Releases should show genres, which are inherited from the parent Game. Releases don't have genres themselves.

Gem for the Steam API: https://github.com/bhaberer/steam-api
Gem for Steam Omniauth: https://github.com/reu/omniauth-steam

We need to figure out how to link between GiantBomb and Steam, Wikidata is a potential option.

Unfortunately it doesn't look like the GiantBomb Wiki includes the Steam URL or ID anywhere, so this may be pretty difficult :/

Dependabot encountered the following error when parsing your .dependabot/config.yml:

The property '#/update_configs/0/automerged_updates/1' of type object did not match one or more of the required schemas

Please update the config file to conform with Dependabot's specification.

You can mention @dependabot in the comments below to contact the Dependabot team.

Let's go with ActiveStorage.

• Does it work on Heroku? Yes

• Should we use Carrierwave along with it? No need, ActiveStorage pretty much handles everything that carrierwave would.

• Any other considerations to make?

  • Will need to figure out how to handle upload storage in production, S3 or Google Cloud probably ;-;

• https://guides.rubyonrails.org/v5.2/active_storage_overview.html

• https://blog.heroku.com/rails-active-storage

• https://evilmartians.com/chronicles/rails-5-2-active-storage-and-beyond

• Keep Rails 6 in mind: https://github.com/rails/rails/blob/v6.0.0.beta1/activestorage/CHANGELOG.md

Add a divider and then the GitHub link below the Sign out button. Not sure if I should have that available for users who aren't signed in as well?

Eventually I'll probably open a Discord server and add that as well.

This would allow for us to automatically keep game data up-to-date and also to get access to identifiers in other databases (e.g. PCGamingWiki, GiantBomb, Wikipedia, etc.).

I'm not sure how to handle games / releases though, Wikidata is inconsistent there, but usually has an item for a given Game rather than its "Release".

Hours played should maybe be limited to ~20k hours to prevent people from adding 10 million hours and messing with the site stats.

I've seen legitimate 10k-ish hours, never much more than that though.

This should be a float to allow for, e.g. 1.5 hour play times.

Use pg_search's multisearch capabilities to provide site-wide search in the navbar.

These might be useful?

• https://getterms.io/ <= this seems like the best one
• https://www.iubenda.com
• https://www.shopify.com/tools/policy-generator
• https://www.shopify.com/tools/policy-generator/terms-and-conditions

I'm not sure exactly how to handle this, companies can be developers and/or publishers. Some companies self-publish, so they're both for a given release.

Most users shouldn't be allowed to delete things, and platforms shouldn't be able to be created/edited by anyone that isn't a moderator.

This is probably dependent on #12?

Games should have release dates. Potentially with a way to show what platforms a given release date refers to.

Dependent on #73.

Releases should always have the same genres as their parent games (please god let this be true, I'm sure Kingdom Hearts screws this up somehow).

Make it possible for moderators and admins to mark a game, release, or company as Protected (like on Wikipedia).

This would make it so only moderators and admins could edit the item.

Right now you can add a release to your library multiple times, which doesn't really make sense. It should be unique.

Probably just need to validate the uniqueness of the release purchase model?

Trending games? A feed of activity?

We probably won’t need this for a while anyway.

https://madewithvuejs.com/charts

This doesn't work:

validates :genres,
  uniqueness: { scope: :id }

Potentially because of the way the association between genres and games is handled currently. It may be a better idea to create a games_genres model to handle these associations, like we have for the release developers/publishers.

Now that we can add a release to the user's library we should also be able to remove it.

For setting release dates, purchase dates, etc.

https://github.com/mariomka/vue-datetime

https://github.com/dbrekalo/vue-date-pick

https://github.com/charliekassel/vuejs-datepicker

With links to the GitHub, my personal site, etc.

Games belong to Series. I'm not sure if we should bother with ordering or just base the order off the release date.

e.g. the Half-Life series has:

• Half-Life
• Half-Life: Blue Shift
• Half-Life: Opposing Force
• Half-Life: Source
• Half-Life 2
• Half-Life 2: Episode One
• Half-Life 2: Episode Two

Whether games like Half-Life Deathmatch should be included, I don't know.

Feature specs can take the place of the request/controller specs, since I haven't really been able to get either to work.

For some reason the request specs are acting up >:( And also there's hardly any documentation out there for request specs.

Maybe just go with feature specs instead, but those are slow.

Unfortunately validations aren't built into ActiveStorage by default so I'll need to work around that limitation.

Should also limit the formats allowed, no WebP (I don't think Safari supports it yet), no gifs (no reason to allow them, game covers don't use GIFs and there's no reason to support them for avatars), and no audio or video formats.

I'd rather not make everything from scratch, so probably should choose an icon library.

• https://ionicons.com/
• https://fontawesome.com/?from=io
• https://material.io/tools/icons/?style=baseline

Wikidata has this as well, it's good for things like Half-Life 2, which is commonly called HL2, or games with different names internationally.

We only need to track dates, no times.

These should probably all be separate issues, but just writing out some thoughts:

• Banning users
  • Should we have temporary bans?
• Reporting users
• Disabling edits after a limit has been reached within a given time period
  • Functionality to lift this edit block and also to automatically have a more strict edit limit for new users vs. users that have contributed before/have had accounts for more than 24 hours.
• Rolling back user edits, for malicious users (see also: https://www.mediawiki.org/wiki/Manual:RollbackEdits.php)
• Protected games, which can only be edited by admins (#68)
• Blocking users (users can block other users, e.g. if they're harassing them)

https://sagalbot.github.io/vue-select/docs/Install.html

Releases should have covers and fallback to the parent Game cover if the release has no release-specific cover.

The problem would be displaying this in a way that's both performant and makes sense to the user.

This application needs tests, dang it. Controller tests, feature tests, integration tests, unit tests. All the tests.

Currently it is... not.

Needs the ability to add a release to your library, and to edit data on it like score, notes, and completion status. And to remove it.

Also add a button on Release pages to add the release to your library.

It should be possible to add it from the Release page, or from the Game page, next to each release (or maybe add a game and then that opens a dropdown that lets you choose the specific release?)

Game purchases can have comments (I should probably rename that to notes), make it possible to add notes to game purchases and also to view them in the user library.

https://github.com/flyerhzm/bullet

Right now we have buttons like this, but it looks rather ugly:

Those buttons aren't used particularly frequently, so they should be hidden behind a dropdown menu.

I think Bulma actually provides this in some capacity already, so we can just use that.

There should probably be a settings controller and one of the pages should be the registrations#edit view, and another for modifying the user's profile (e.g. the user bio and eventually the user avatar). Either the content should be submitted via AJAX (to allow the user to, e.g. change their email and password separately), or each different thing you can change would need to be on a separate page.

users/edit can probably be removed as an accessible view.

https://github.com/prettier/eslint-config-prettier

https://github.com/vuejs/eslint-plugin-vue

https://prettier.io/

https://github.com/rails/webpacker

See the discussion here: https://github.com/rails/webpacker/pull/1755/files

Will need to upgrade to Webpack 4.x, @rails/webpacker 4.x, webpacker (the gem) 4.x, and maybe webpack-dev-server 3.x.

• Log in and go to settings/account
• Submit the account details form with an error (e.g. press update without changing anything)
• Note that you've been redirected to users/edit and the page is unstyled (this is because there's no view in the users/registrations directory for user/edit)

I'll need to override the default devise controller method for this somehow.

Need to figure out a few things:

• Probably Heroku
• Hobby dynos are probably fine for now
• We'll definitely need the 10M rows in Postgres
• We'll need a mail provider
• We'll need a way to store ActiveStorage attachments

https://github.com/varvet/pundit

https://crypt.codemancers.com/posts/2018-07-29-leveraging-pundit/

https://www.thunderboltlabs.com/blog/2013/03/27/testing-pundit-policies-with-rspec/

https://code.tutsplus.com/tutorials/authorization-with-pundit--cms-28202