destinia / vision Goto Github PK

Currently we use redux-firestore and react-redux-firebase to connect to data sources, and the state is in the shape of

{
  "firebase": {
    "data": { ... },
     ...
  },
  "firestore": {
    "data": { ... },
     ...
  },
  ...
}

We should redesign the state shape, as it doesn't make sense If the data source is changed.

Currently (as in PR #3 ) each sequence is store in one document, in the format of

{
  name: '<seq name>',
  values: [
    {
      timestamp: '<timestamp>',
      value: '<value>'
    },
    ...
  ]
}

and all documents live in a single collection. I think we can create different collections for development and production environments.

Any idea or comment about the format of sequences? Is there any other information we need to store?

• editor (react codemirror)
• remove chart
• lock chart
• navbar (import export)
• aggregate
• undo/redo

1. Create a test backend server that generates fake data in a given pattern at a given frequency.
2. The configuration file for Firestore should be language independent.

For human-editable configuration format

# chart-id should be a unique, valid name
chart:
  # (required)
  title: "Title"

  # (optional)
  description: "Some description"

  # Multiple sources (optional)
  sources:
    - name: "source-name"
      type: "chart type"

    - name: "source-name"
      type: "chart type"

    - name: "source-name"
      type: "chart type"

  # Data is filtered to be in the range of [start, end]
  # Both start & end is in RFC3339 format

  # (optional, default to the first data)
  # If start is negative, it means the offset from end
  start: -3600

  # (optional, default to now)
  end: 2018-07-28T07:32:00Z

  # (optional, only useful when agg_func is set)
  segment: 60

  # (optional)
  agg_func: "average"

Procedures to reproduce

1, switch to branch navbar
2. npm run start
3. click download to save a snapshot of the current layout.
4. randomly change layout
5. click upload to load the previous saved layout

A possible solution

Use versioning: feed key={timestamp} so that React will be forcibly re-create the grid. This may solve to problem (we have to try...)

Related issues

here and here