/query endpoint roadmap

[adrianmroz-allegro]

Draft

Required

• Ajax new static method Use /query endpoint in visualisation #1023
  • Should have partially applied AppSettings
  • Should be distributed in context
  • Remove Ajax.version and Ajax.settingsVersion
• /query endpoint feature/query endpoint backend #1022
  • Introduce some dispatch for different query generation methods and/or different request schemas
  • Extract some validation logic that could be shared between /query, /mkurl and plywood
  • Move to common deserialization methods (/query and /mkurl need right now to convert app settings/data cube to client versions)
• Endpoints
  • Visualisation Use /query endpoint in visualisation #1023
  • Raw data modal Query endpoint: Raw data modal #1025
  • Boolean filter feature/boolean filter query endpoint #1024
  • Preview String filter
  • Selectable String filter
  • Numeric filter

Nice to have (ordered by priority and complexity)

• Rewrite fetching logic in components using hooks (look for client usages of DataCube.executor!)
  • Hook for comparing previous essence
  • Hook for debounced fetch
  • Handle aborted DatasetRequests - right now we have some wierd null
• Remove Ajax.query and whole static class - functions are better
• Remove plywood fields from ClientDataCube (and ClientMeasure ...), if needed introduce simple fields like isApproximate instead of inspecting expressions
• Introduce some mechanism for easy access to three objects - view definition, essence and hash on client. They are just three different views on the same data
• Create ClientEssence and ServerEssence
  • ClientEssence has additional UI fields like pinned measures, measure formats
  • ServerEssence can be simple POJsO with few convenience accessors - it is an ephemeral object, that's created for each request and destroyed after