You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@senssoft.apache.org by "Arthi Vezhavendan (JIRA)" <ji...@apache.org> on 2017/08/30 17:38:03 UTC
[jira] [Resolved] (SENSSOFT-243) Investigation how much scope is
required to build Sankey as js or react module
[ https://issues.apache.org/jira/browse/SENSSOFT-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arthi Vezhavendan resolved SENSSOFT-243.
----------------------------------------
Resolution: Resolved
We're going to continue to build this out as a react module for now. This path is a easier now that I've fixed the dev environment structure. Also, undoing the components for filtering and the bar graphs is not a trivial level of effort. Instead, I'll work with Ryan to bring in the sankey as it's own module.
> Investigation how much scope is required to build Sankey as js or react module
> ------------------------------------------------------------------------------
>
> Key: SENSSOFT-243
> URL: https://issues.apache.org/jira/browse/SENSSOFT-243
> Project: SensSoft
> Issue Type: Sub-task
> Components: TAP
> Affects Versions: Tap 0.1.0
> Environment: javascript/react
> Reporter: Joshua Poore
> Assignee: Arthi Vezhavendan
> Fix For: Tap 0.1.0
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> We need to understand what the path of least resistance is: do we build out this demo as a react module, or as a javascript build.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)