Emi Matchu ed5b62e161 Use PetType's created_at to predict who an item might be compatible with ... This is a basic attempt at the Vandagyre logic, but also things like "Maraquan items released before the Maraquan X was released"! I also added a new task, `rails items:update_cached_fields`, which needs to be run after this change, because it affects the value of `Item#predicted_fully_modeled?`. Eyeballing the updated search results for `-is:modeled`, this feels pretty close? I'm guessing it's not perfect (e.g. maybe a pet type we got modeled late into its existence, or some items that just never did fit a certain pet), but feels pretty good. I also know we had the "modeling hints" override in Impress 2020, which we aren't reading yet. We should probably take that into account here too!		2024-11-19 16:41:50 -08:00
..
fixtures	Use PetType's created_at to predict who an item might be compatible with	2024-11-19 16:41:50 -08:00
models	Use PetType's created_at to predict who an item might be compatible with	2024-11-19 16:41:50 -08:00
services	Improve Solargraph LSP in our spec files	2024-11-19 11:28:36 -08:00
support	Add failing test for modeling bug where we break existing connections	2024-11-06 14:08:32 -08:00
rails_helper.rb	Move modeling tests to RSpec	2024-10-21 16:03:58 -07:00
spec_helper.rb	Use alias they in specs instead of it, when it reads better	2024-10-25 13:38:02 -07:00