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
a GUI tool for reading the topic/queues. at KFC we used Azure Service Bus as our pubsub and I remember relying heavily on the GUI tool for inspecting messages in the queue for production debugging. just a thought! thanks again
The text was updated successfully, but these errors were encountered:
Would be good for this interface to support filtering. Kendall also suggested SQL-like syntax for more advanced filtering. We've discussed this in the past already for the graph view for security review, and also discussed threading that through more of the console/cli, so this definitely warrants further thought/discussion.
Main trade-offs off the top of my head:
Change in how we add new filterable-attributes to user-facing record types from: straightforward backend change followed by a DX person making a ConsoleService API change + UI change --> straightforward backend change + some sort of config/annotation/directive/similarly-easy change denoting whether the new attribute should be exposed to users + console/cli sql interface picks it up automatically and no changes needed for console API or UI.
Broadly re-usable SQL-like interface in the console, so we don't need to build custom filters for each attr
Easy to pack tons and tons of filtering capability into a tiny amount of UI real estate
SQL-like filters tend to be unfriendly to less technical users / non-power users. Discoverability of filterable attributes is also hard, unless we make the whole view's schema both accessible and grokkable.
Probably would want to just create a view that's a restricted subset of FTL's actual database contents, restricted based on what we want users to actually have access to, and let them hit that directly with the psql dialect. We do not want our own SQL dialect. oheckno.
From @KendallWeihe:
The text was updated successfully, but these errors were encountered: