To add bit more to what Ruwini has explained..
Universal widget currently reads the provider configuration and fetches
data from the data source and render the vizgrammar chart using the fetched
data according to the chart configuration.
In the proposed approach we will still keep the provider
Hi,
If we use the name 'UniversalWidget' instead of 'ParentRenderer' as shown
below, it will eliminate the backward compatibility issue.
*-universal-widget*
*-vizgrammar-renderer*
*-search-renderer*
Appreciate your thoughts on this approach.
Thanks,
Regards,
Ruwini
On Fri, Sep 21, 2018 at
Hi Sajith,
Thanks for the response.
I'll proceed with this approach.
Thanks,
Regards,
Ruwini
On Fri, Sep 21, 2018 at 9:44 AM Sajith Ariyarathna
wrote:
> +1 for 2nd approach.
> +1 for suggested migration implementation.
>
> Thanks.
>
> On Fri, Sep 21, 2018 at 9:38 AM Ruwini Wijesiri wrote:
>
+1 for 2nd approach.
+1 for suggested migration implementation.
Thanks.
On Fri, Sep 21, 2018 at 9:38 AM Ruwini Wijesiri wrote:
> Hi Tanya,
>
> Thank you for the response.
>
> I think its better to handle this at the dashboard level by making "
>> *UniversalWidget*" a reserved word and
Hi Tanya,
Thank you for the response.
I think its better to handle this at the dashboard level by making "
> *UniversalWidget*" a reserved word and replacing it with "
> *vizgrammar-renderer" *in the Dashboard json before passing it to Golden
> Layout. So that customers don't need to bother
Hi All,
The widget generation wizard enables user to create widgets by configuring
a data source and publisher information.
We have a requirement to enable user to create a autocomplete search bar
using the widget generation wizard. The user will specify a column of the
configured data source
