impress/spec/fixtures/colors.yml

blue:
  id: 8
  name: blue
purple:
  id: 57
  name: purple
robot:
  id: 62
  name: robot
striped:
  id: 77
  name: striped
swamp_gas:
  id: 93
  name: "swamp gas"
Add failing test for modeling bug where we break existing connections As I'm writing out my solution for this, I'm almost wondering if it's time for the refactor I've been Theoretically Planning Someday, to move items to a real `ItemAppearance` model in the database similar to `PetState`… Hmm hmm hmm… For now though, I'm taking a break! 2024-11-06 14:08:32 -08:00			`blue:`
			`id: 8`
			`name: blue`
Basic modeling test! Just getting a basic foothold here. I'm thinking about moving this to RSpec, cuz I feel like the assertions are gonna get pretty specific and groupable. 2024-10-21 14:05:10 -07:00			`purple:`
			`id: 57`
			`name: purple`
Add alt style modeling tests I didn't do the assets part of it yet, just the style object! 2024-10-29 22:20:43 -07:00			`robot:`
			`id: 62`
			`name: robot`
Basic modeling spec for my pet, matts_bat No items yet, just putting in the very basics of biology, more shortform than the Thyassa case 2024-10-24 15:37:57 -07:00			`striped:`
			`id: 77`
			`name: striped`
Handle new colors/species in the Rainbow Pool Oh right, yeah, we like to do things gracefully around here when there's no corresponding color/species record yet! Paying more attention to this, I'm thinking like… it could be a cool idea to, in modeling, create the new color/species record, and just not have all the attributes filled in yet? Especially now that we're less dependent on attributes like `standard` to be set for correct functioning. But for now, we follow the same strategy we do elsewhere in the app: a pet type can have `color_id` and `species_id` that don't correspond to a real record, and we cover over that smoothly. 2024-11-15 19:56:07 -08:00			`swamp_gas:`
			`id: 93`
			`name: "swamp gas"`