Spike: determine the effort required to include a Cube playground in Angular - Githubissues

dotCMS / core

Headless/Hybrid Content Management System for Enterprises

http://dotcms.com

Other

846 stars 465 forks source link

Spike: determine the effort required to include a Cube playground in Angular #29969

Open dsilvam opened 1 week ago

dsilvam commented 1 week ago

Parent Issue

No response

Task

There's the need to offer querying capabilities to the users of Content Analytics and providing a query builder for CubeJS would provide a better UX.

This task is to determine the effort required to include a Cube playground as a portlet in the dotCMS backend.

There this blog where they describe how to implement something like this that we might find useful https://cube.dev/blog/angular-dashboard-tutorial-with-cubejs.

Proposed Objective

Core Features

Proposed Priority

Priority 2 - Important

Acceptance Criteria

Having an estimate of the effort required to include the Cube playground as a portlet in our backend.

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

No response

Assumptions & Initiation Needs

No response

Quality Assurance Notes & Workarounds

No response

Sub-Tasks & Estimates

No response

hmoreras commented 8 hours ago

Findings:

Cube has a playground itself, but as they mention is not recommend to exposed out of dev mode, so they offers the options to expose their data one is via a SDK for Angular that helps for query and visualization of data.

We will need to implement the playground using the layout and graphics or our choice.

[ ] Design of the playground.
[ ] Implement the graphics and how to show and filter the results.