d50aae87a5
#### TODO
- [x] fix `hashable >= 1.3.1` serialization ordering issue [^1]
- `test_graphql_mutations.py::TestGraphQLMutateEnums` was failing
- [x] fix `unordered-containers` serialization ordering issue [^2]
- `test_graphql_queries.py` was failing on Citus
- [ ] verify that no new failures have been introduced
- [ ] open issues to fix the above
- identify test cases that "leak" implementation details by depending on `hashable` instance ordering
- bump `hashable >= 1.3.1` and update test cases with new ordering OR modify them so that ordering is stable
- bump `unordered-containers >= 0.2.15.0` and update test cases with new ordering OR modify them so that ordering is stable
- one of the test cases was failing on string equality comparison for a generated Citus query
- we probably don't want to _actually_ do this unless there are _very specific_ guarantees we want to make about generated query structure
---
Just what it says on the tin.
https://github.com/hasura/graphql-engine-mono/pull/3538 updated the freeze file a few weeks ago, but it looks like the index state hadn't been updated since December so a lot of stuff that had newer versions didn't get updated.
---
EDIT: I should add, the motivation for doing this in the first place is that `hspec > 2.8.4` now supports specifying filtering spec trees based on patterns provided by the `HSPEC_MATCH` environment variable.
For example, one could have a script that executes the following:
```
HSPEC_MATCH="PostgreSQL" \
ghcid \
--command \
'cabal repl graphql-engine:test:tests-hspec \
--repl-option -O0 \
--repl-option -fobject-code' \
--test "main"
```
...which will loop on typechecking the `tests-hspec` component, and then as soon as it passes (i.e. no warnings or errors) will run _only_ the `PostgreSQL` sub-components.
[^1]: `hashable >= 1.3.1.0` [updated its default salts](https://github.com/haskell-unordered-containers/hashable/pull/196), which [broke serialization ordering](https://github.com/haskell/aeson/issues/837)
[^2]: `unordered-containers >= 0.2.16.0` [introduced changes to some of its internal functions](https://hackage.haskell.org/package/unordered-containers-0.2.16.0/changelog) which seem like they could have affected serialization stability
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/3672
GitOrigin-RevId: bbd1d48c73db4021913f0b5345b7315a8d6525d3
|
||
|---|---|---|
| .circleci | ||
| .github | ||
| architecture | ||
| assets | ||
| cli | ||
| cli-ext | ||
| community | ||
| console | ||
| contrib/metadata-types | ||
| docker-compose | ||
| docs | ||
| install-manifests | ||
| rfcs | ||
| scripts | ||
| server | ||
| translations | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .hlint.yaml | ||
| .kodiak.toml | ||
| cabal.project | ||
| cabal.project.ci | ||
| cabal.project.ci-haddock | ||
| cabal.project.ci-haddock.freeze | ||
| cabal.project.ci-haddock.local | ||
| cabal.project.ci.freeze | ||
| cabal.project.ci.local | ||
| cabal.project.dev | ||
| cabal.project.dev-sh | ||
| cabal.project.dev-sh.freeze | ||
| cabal.project.dev-sh.local | ||
| cabal.project.freeze | ||
| CHANGELOG.md | ||
| code-of-conduct.md | ||
| CONTRIBUTING.md | ||
| docker-compose.yml | ||
| event-triggers.md | ||
| LICENSE | ||
| LICENSE-community | ||
| Makefile | ||
| package-lock.json | ||
| README.md | ||
| remote-schemas.md | ||
| sample.hie.yaml | ||
| SECURITY.md | ||
Hasura GraphQL Engine
Hasura is an open source product that accelerates API development by 10x by giving you GraphQL or REST APIs with built in authorization on your data, instantly.
Read more at hasura.io and the docs.
Features
- Make powerful queries: Built-in filtering, pagination, pattern search, bulk insert, update, delete mutations
- Works with existing, live databases: Point it to an existing database to instantly get a ready-to-use GraphQL API
- Realtime: Convert any GraphQL query to a live query by using subscriptions
- Merge remote schemas: Access custom GraphQL schemas for business logic via a single GraphQL Engine endpoint. Read more.
- Extend with Actions: Write REST APIs to extend Hasura’s schema with custom business logic.
- Trigger webhooks or serverless functions: On Postgres insert/update/delete events (read more)
- Scheduled Triggers: Execute custom business logic at specific points in time using a cron config or a one-off event.
- Fine-grained access control: Dynamic access control that integrates with your auth system (eg: auth0, firebase-auth)
- Admin UI & Migrations: Admin UI & Rails-inspired schema migrations
- Supported Databases: Supports PostgreSQL (and its flavours), MS SQL Server and Big Query. Support for more databases coming soon.
Read more at hasura.io and the docs.
Table of contents
Table of Contents
- Quickstart:
- Architecture
- Client-side tooling
- Add business logic
- Demos
- Support & Troubleshooting
- Stay up to date
- Contributing
- Brand assets
- License
- Translations
Quickstart:
One-click deployment on Hasura Cloud
The fastest and easiest way to try Hasura out is via Hasura Cloud.
-
Click on the following button to deploy GraphQL engine on Hasura Cloud including Postgres add-on or using an existing Postgres database:
-
Open the Hasura console
Click on the button "Launch console" to open the Hasura console.
-
Make your first GraphQL query
Create a table and instantly run your first query. Follow this simple guide.
Other one-click deployment options
Check out the instructions for the following one-click deployment options:
| Infra provider | One-click link | Additional information |
|---|---|---|
| Heroku |  |
docs |
| DigitalOcean |  |
docs |
| Azure |  |
docs |
| Render |  |
docs |
Other deployment methods
For Docker-based deployment and advanced configuration options, see deployment guides or install manifests.
Architecture
The Hasura GraphQL Engine fronts a Postgres database instance and can accept GraphQL requests from your client apps. It can be configured to work with your existing auth system and can handle access control using field-level rules with dynamic variables from your auth system.
You can also merge remote GraphQL schemas and provide a unified GraphQL API.
Client-side tooling
Hasura works with any GraphQL client. See awesome-graphql for a list of clients. Our frontend tutorial series also have integrations with GraphQL clients for different frameworks.
Add business logic
GraphQL Engine provides easy-to-reason, scalable and performant methods for adding custom business logic to your backend:
Remote schemas
Add custom resolvers in a remote schema in addition to Hasura's database-based GraphQL schema. Ideal for use-cases like implementing a payment API, or querying data that is not in your database - read more.
Actions
Actions are a way to extend Hasura’s schema with custom business logic using custom queries and mutations. Actions can be added to Hasura to handle various use cases such as data validation, data enrichment from external sources and any other complex business logic - read more
Trigger webhooks on database events
Add asynchronous business logic that is triggered based on database events. Ideal for notifications, data-pipelines from Postgres or asynchronous processing - read more.
Derived data or data transformations
Transform data in Postgres or run business logic on it to derive another dataset that can be queried using GraphQL Engine - read more.
Demos
Check out all the example applications in the community/sample-apps directory.
Realtime applications
-
Group Chat application built with React, includes a typing indicator, online users & new message notifications.
-
Live location tracking app that shows a running vehicle changing current GPS coordinates moving on a map.
-
A realtime dashboard for data aggregations on continuously changing data.
Videos
- Add GraphQL to a self-hosted GitLab instance (3:44 mins)
- Todo app with Auth0 and GraphQL backend (4:00 mins)
- GraphQL on GitLab integrated with GitLab auth (4:05 mins)
- Dashboard for 10million rides with geo-location (PostGIS, Timescale) (3:06 mins)
Support & Troubleshooting
The documentation and community will help you troubleshoot most issues. If you have encountered a bug or need to get in touch with us, you can contact us using one of the following channels:
- Support & feedback: Discord
- Issue & bug tracking: GitHub issues
- Follow product updates: @HasuraHQ
- Talk to us on our website chat
We are committed to fostering an open and welcoming environment in the community. Please see the Code of Conduct.
If you want to report a security issue, please read this.
Stay up to date
We release new features every month. Sign up for our newsletter by using the link below. We send newsletters only once a month. https://hasura.io/newsletter/
Contributing
Check out our contributing guide for more details.
Brand assets
Hasura brand assets (logos, the Hasura mascot, powered by badges etc.) can be found in the assets/brand folder. Feel free to use them in your application/website etc. We'd be thrilled if you add the "Powered by Hasura" badge to your applications built using Hasura. ❤️
<!-- For light backgrounds -->
<a href="https://hasura.io">
<img width="150px" src="https://graphql-engine-cdn.hasura.io/img/powered_by_hasura_primary_darkbg.svg" />
</a>
<!-- For dark backgrounds -->
<a href="https://hasura.io">
<img width="150px" src="https://graphql-engine-cdn.hasura.io/img/powered_by_hasura_primary_lightbg.svg" />
</a>
License
The core GraphQL Engine is available under the Apache License 2.0 (Apache-2.0).
All other contents (except those in server, cli and
console directories) are available under the MIT License.
This includes everything in the docs and community
directories.
Translations
This readme is available in the following translations:
- Japanese 🇯🇵 (🙏 @moksahero)
- French 🇫🇷 (🙏 @l0ck3)
- Bosnian 🇧🇦 (🙏 @hajro92)
- Russian 🇷🇺 (🙏 @highflyer910)
- Greek 🇬🇷 (🙏 @MIP2000)
- Spanish 🇲🇽(🙏 @ferdox2)
- Indonesian 🇮🇩 (🙏 @anwari666)
- Brazilian Portuguese 🇧🇷 (🙏 @rubensmp)
- German 🇩🇪 (🙏 @FynnGrandke)
- Chinese 🇨🇳 (🙏 @jagreetdg & @johnbanq)
- Turkish 🇹🇷 (🙏 @berat)
- Korean 🇰🇷 (🙏 @라스크)
Translations for other files can be found here.