You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the new recent item picker, we're going to need some changes to the activity/recents api
We need to track the most recent 20 items that each user has "touched" (ie viewed) of each entity type
question
model
table (probably don't need right now)
dashboard
collection
for a collection to be "recently viewed" means that:
the collection was created
a dashboard or question was saved in the collection
a dashboard, question, or collection was moved into the collection
We also need more information about each item than the current api provides
can_write
last_touched or some sort of proxy for sorting by most recently used (i think this is what the timestamp field in the recent_views table is doing)
parent information - collection name + authority level (eventually parent db for tables)
While we're at it, can we make the payload for the recents endpoint conform more closely to search and/or collection items?
nesting model_object inside each recent item is a weird pattern that's used nowhere else and is completely unnecessary, we can just populate a model property on each item like we do elsewhere
we should probably update the popular items api to match
Desired RecentItem Shape
(open to discussion)
interfaceRecentItem{id: number;name: string;model: string;// should differentiate between regular cards and "dataset" for modelscan_write: boolean;display: string;// for questionsparent_collection: {// for non-tablesid: number;name: string;authority_level: "official"|null;// for collections}|null;database: {// for tablesid: number;name: string;// display name}|null;authority_level: "official"|null;// for collectionsmoderated_status: "verified"|null;// for modelstimestamp: string;// last touched}
The content you are editing has changed. Please copy your edits and refresh the page.
related to #39528
product doc
For the new recent item picker, we're going to need some changes to the activity/recents api
can_write
last_touched
or some sort of proxy for sorting by most recently used (i think this is what the timestamp field in the recent_views table is doing)model_object
inside each recent item is a weird pattern that's used nowhere else and is completely unnecessary, we can just populate amodel
property on each item like we do elsewhereDesired RecentItem Shape
(open to discussion)
Tasks
The text was updated successfully, but these errors were encountered: