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
The grid would show the entry_id, the type (shown as the panel name), created and a summary of the data-entry that would be provided by the panel itself.
Idea was to split off the summary for the panel labels into a separate function getSummaryStats()-function to also show info in the grid (eg a database entry could show: "80 queries, 1005ms")
Still to be determined:
Is it worth it?
Should this be made searchable (aside from the filters for the type etc)? If so, how? (We don't want to needlessly pile on more data to insert during logging)
Anything else?
The text was updated successfully, but these errors were encountered:
Yes, it would be really nice to see some of the panel data on its own. It means things like curl dont need their own tables.
Should this be made searchable (aside from the filters for the type etc)? If so, how? (We don't want to needlessly pile on more data to insert during logging)
It would be nice to search things like the curl URL. Perhaps data should have a varchar(255) called keywords. We then ask the panel to give Panel::saveKeywords(), or we change Panel::save() to return an array (eg: ['data'=>$data,'keywords'=>$keywords]). I prefer the later as it allows future changes without changing all the panels.
Anything else?
Nothing I can think of right now. But I'll surely come up with something once its done! :)
The grid would show the
entry_id
, thetype
(shown as the panel name),created
and a summary of the data-entry that would be provided by the panel itself.Idea was to split off the summary for the panel labels into a separate function
getSummaryStats()
-function to also show info in the grid (eg a database entry could show: "80 queries, 1005ms")Still to be determined:
The text was updated successfully, but these errors were encountered: