sirix-web-frontend
sirix-web-frontend copied to clipboard
A web front-end for SirixDB based on Nuxt.js/Vue.js, D3.js and Typescript
Bumps [inversify-props](https://github.com/CKGrafico/inversify-props) from 1.5.0 to 2.0.1. Commits See full diff in compare view [](https://dependabot.com/compatibility-score/?dependency-name=inversify-props&package-manager=npm_and_yarn&previous-version=1.5.0&new-version=2.0.1) Dependabot will resolve any conflicts with this PR as long as you don't alter...
Bumps [serialize-javascript](https://github.com/yahoo/serialize-javascript) from 2.1.2 to 3.0.0. Release notes Sourced from serialize-javascript's releases. v3.0.0 Introduce support for Infinity (@vthibault, #72) Bump mocha from 7.0.0 to 7.0.1 (#71) Test on Node.js v12...
Bumps [@nuxtjs/pwa](https://github.com/nuxt-community/pwa-module) from 3.0.0-beta.19 to 3.0.0-beta.20. Changelog Sourced from @nuxtjs/pwa's changelog. 3.0.0-beta.20 (2020-02-02) Commits 0ab89e0 chore(release): 3.0.0-beta.20 d7d1beb chore(deps): remove duplicate fs-extra dependency 0f32a44 chore(deps): update defu to 1.0.0 9a8018d...
Have to read about how to test the frontend stuff... besides Unit Tests for some stuff.
Displaying databases and resources in a TreeView similarly to other database system front-end as for instance pgadmin. We can use the password credentials flow in the first place with an...
In the long run I think it might be better to only have TypeScript based files.
We want to be able to display huge JSON and XML instances (provide an overview), that is one revision. Then it's all about visualizing the changes between revisions: In a...
See: https://github.com/nuxt/typescript/issues/49 I did the workaround locally mentioned in https://github.com/nuxt/typescript/issues/49#issuecomment-531086770 However, I hope that gets fixed. Either from the Element-UI or Next.js developers...
What do you think about using the new composition API from Vue.js?
As SirixDB is able to store `Integer.MAX - 1` revisions, we have to take paging into account. So the table should be loaded at first with the metadata from `most-recent-revision-number`...