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
{{ message }}
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
At the moment, a request to Falcon's GET /queries returns an array of query objects {requestor, fid, uids, refreshInterval, query, connectionId} that doesn't include grid name.
The proposal here is that we ensure the returned query objects include the property filename. With this approach, #472 wouldn't need additional code to request the grid names.
@tarzzz I imagine that for a given fid, the grid name (filename?) can change (i.e. users are allowed to rename the grid without changing its fid). Is that so?
If this is the case, there is no point in saving the grid name in Falcon's queries.yml. Instead, requests to GET /queries and GET /queries/:fid should trigger requests to getGridMeta.
@n-riesco You should be able to use: https://api.plot.ly/v2/folders#all (with the query-parameter as grid ) to get all the grids for that user.. (which can then be filtered for the fid from falcon .. !!
That will also be very expensive if there are many grids... some users have 10k grids
True. Unfortunately, we don't have any endpoint at the moment which takes a list of fids and return only their metadata.. !! Either we can list them all, or we can get them iteratively using detail endpoint.. !!
Activity
nicolaskruchten commentedon Jul 3, 2018
This could get expensive if there are 100 queries, that's 100 calls to the API right?
tarzzz commentedon Jul 3, 2018
That's correct.
n-riesco commentedon Jul 3, 2018
https://api.plot.ly/v2/grids#lookup doesn't support listing all files :(
tarzzz commentedon Jul 3, 2018
@n-riesco You should be able to use: https://api.plot.ly/v2/folders#all (with the query-parameter as
grid) to get all the grids for that user.. (which can then be filtered for thefidfrom falcon .. !!nicolaskruchten commentedon Jul 3, 2018
That will also be very expensive if there are many grids... some users have 10k grids
nicolaskruchten commentedon Jul 3, 2018
What we would need is to ask the API "what are the names of these N fids?"
tarzzz commentedon Jul 3, 2018
True. Unfortunately, we don't have any endpoint at the moment which takes a list of
fids and return only their metadata.. !! Either we can list them all, or we can get them iteratively usingdetailendpoint.. !!nicolaskruchten commentedon Jul 3, 2018
Yep, and what I'm saying is that neither of these are going to be great from a performance POV.