b167aa84d1
I set up a local PostgreSQL read replica, loaded the Chinook dataset, and poked around finding bugs here and there. I added `read_only: true` to the relevant SQL queries to mitigate these. I did not test exhaustively or even that well, and I only tried this with PostgreSQL, so I am sure that I have missed some, but this at least seems to make the console's Data tab usable. Note that this removes the check for the `READ_ONLY_RUN_SQL_QUERIES` feature flag, which seems pointless, as it's checking whether we're running v1.1.0 of the HGE server or later. I sincerely hope no one is actually running such an old version. If this change is acceptable, we can probably remove the feature flag logic entirely, but that is not something I want to do here. [DSF-218]: https://hasurahq.atlassian.net/browse/DSF-218?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/8451 Co-authored-by: Luca Restagno <59067245+lucarestagno@users.noreply.github.com> GitOrigin-RevId: 5f4ebfa8f44e2921071699085b877db78aaa4e24 |
||
|---|---|---|
| .. | ||
| .husky | ||
| .storybook | ||
| .vscode | ||
| apps | ||
| docker | ||
| docs | ||
| libs | ||
| static | ||
| tools | ||
| types | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .lintstagedrc.mjs | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc | ||
| babel.config.json | ||
| control-plane-graphql-codegen.yml | ||
| custom-webpack.config.js | ||
| frontend.code-workspace | ||
| jest.preset.js | ||
| nx.json | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| tailwind.config.js | ||
| tsconfig.base.json | ||
Frontend
This project was generated using Nx.
Visit the Nx Documentation to learn more about it.
This frontend monorepo contains the Hasura Console, in all the possible modes.
Last import 2023-01-12
Nx Console
It's highly recommended to install the Nx Console for VSCode, IntelliJ or Neovim.
It will allow you to have all of the Nx commands usable via UI, have an embedded view of the NX graph right in your editor, and much more.
Hasura Console
The Hasura Console is an admin dashboard to manage the connected database and to try out GraphQL APIs. It is a React application bundled with Webpack, and the state is managed mostly using Redux.
Table of contents
- Generic info
- Coming from the previous codebase
- Development Tooling
- Design System's Storybook
- Cypress Dashboard
- Cypress README
How to
Install the dependencies
Run npm install.
Development server
Run nx serve console-ce (requires an .env file) for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.
Build
Run nx build console-ce to build the project. The build artifacts will be stored in the dist/ directory.
Running unit tests
Run nx test console-ce to execute the unit tests via Jest.
Run nx affected:test to execute the unit tests affected by a change.
Running end-to-end tests
Run nx e2e console-ce-e2e --watch (requires an .env file) to open the Cypress UI and locally working with it.
Run nx e2e console-ce-e2e (requires an .env file) to execute the end-to-end tests via Cypress.
Run nx affected:e2e (requires an .env file) to execute the end-to-end tests affected by a change.
Understand your workspace
Run nx graph to see a diagram of the dependencies of your projects.