impress/app/controllers/item_appearances_controller.rb

class ItemAppearancesController < ApplicationController
	def index
		@item = Item.find(params[:item_id])
		render json: @item.as_json(
			only: [:id], methods: [:appearances, :restricted_zones]
		)
	end
end
Replace swf_assets#index with item_appearances#index Preparing a better endpoint for wardrobe-2020 to use! I deleted the now-unused swf_assets#index endpoint, and replaced it with an "appearances" concept that isn't exactly reflected in the database models but is a _lot_ easier for clients to work with imo. Note that this was a big part of the motivation for the recent `manifest_url` work—in this draft, I'm probably gonna have the client request the manifest, rather than use impress-2020's trick of caching it in the database! There's a bit of a perf penalty, but I think that's a simpler starting point, and I have a hunch I'll be able to make up the perf difference once we have the impress-media-server managing more of these responsibilities. 2023-11-11 07:14:48 -08:00			`class ItemAppearancesController < ApplicationController`
			`def index`
			`@item = Item.find(params[:item_id])`
Load item page restricted zones data from Rails app, not impress-2020 Just moving more stuff over! I modernized Item's `as_json` method while I was here. (Note that I removed the NC/own/want fields, because I think the only other place this method is still called from is the quick-add feature on the closet lists page, and I think it doesn't use these fields to do anything: updating the page is basically a full-page reload, done sneakily.) 2023-11-11 08:41:31 -08:00			`render json: @item.as_json(`
			`only: [:id], methods: [:appearances, :restricted_zones]`
			`)`
Replace swf_assets#index with item_appearances#index Preparing a better endpoint for wardrobe-2020 to use! I deleted the now-unused swf_assets#index endpoint, and replaced it with an "appearances" concept that isn't exactly reflected in the database models but is a _lot_ easier for clients to work with imo. Note that this was a big part of the motivation for the recent `manifest_url` work—in this draft, I'm probably gonna have the client request the manifest, rather than use impress-2020's trick of caching it in the database! There's a bit of a perf penalty, but I think that's a simpler starting point, and I have a hunch I'll be able to make up the perf difference once we have the impress-media-server managing more of these responsibilities. 2023-11-11 07:14:48 -08:00			`end`
			`end`