`spawn-dc-sqlite-agent` was incorrectly named, and the `start-dc-sqlite-agent` target was missing. In addition, we usually only make the `start-xyz` target public in `make help`, and so only that needs a comment.
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5804
GitOrigin-RevId: 8064ce148d004ef73dbd8570ef30435423ede0a1
Where possible, we start the services on random ports, to avoid
port conflicts when parallelizing tests in the future.
When this isn't possible, we explicitly state the port, and wait for the
service to start. This is typically because the GraphQL Engine has already
started with knowledge of the relevant service passed in through an
environment variable.
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5542
GitOrigin-RevId: b51a095b8710e3ff20d1edb13aa576c5272a5565
This separates out the dependencies from the server builder.
I am using Python 3.9 as it has improved support for type annotations, which I would like to use.
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5761
GitOrigin-RevId: d57b4a5ace050861e516dd79a4a38ff4844d4093
### Description
This PR changes all the schema code to operate in a specific `SchemaT` monad, rather than in an arbitrary `m` monad. `SchemaT` is intended to be used opaquely with `runSourceSchema` and `runRemoteSchema`. The main goal of this is to allow a different reader context per part of the schema: this PR also minimizes the contexts. This means that we no longer require `SchemaOptions` when building remote schemas' schema, and this PR therefore removes a lot of dummy / placeholder values accordingly.
### Performance and stacking
This PR has been through several iterations. #5339 was the original version, that accomplished the same thing by stacking readers on top of the stack at every remote relationship boundary. This raised performance concerns, and @0x777 confirmed with an ad-hoc test that in some extreme cases we could see up to a 10% performance impact. This version, while more verbose, allows us to unstack / re-stack the readers, and avoid that problem. #5517 adds a new benchmark set to be able to automatically measure this on every PR.
### Remaining work
- [x] a comment (or perhaps even a Note?) should be added to `SchemaT`
- [x] we probably want for #5517 to be merged first so that we can confirm the lack of performance penalty
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5458
GitOrigin-RevId: e06b83d90da475f745b838f1fd8f8b4d9d3f4b10
## Description 🔖
This PR add 2 hooks required for the new allow list manager
- useAddCollectionToAllowList
- useRemoveCollectionFromAllowList
and integrate them into the QueryCollectionHeader component.
I also moved QueryCollectionHeader component under QueryCollections folder
## Review Setup 💻
- [ ] Run Storybook
## Review checklist. 📋
- [ ] Check useAddToAllowList hook story
- [ ] Check useRemoveFromAllowList hook story
- [ ] Check QueryCollectionHeader story
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5771
GitOrigin-RevId: aaee4a44602a54e374522924d8e3afe7e837d2c7
>
## Description ✍️
This PR adds the architecture deep dive of streaming subscriptions and benchmarks for up to 1M active subscriptions.
### Kodiak commit message
Information used by [Kodiak bot](https://kodiakhq.com/) while merging this PR.
#### Commit title
architecture: add streaming subscriptions
#### Commit body
(Append below if you want to add something to the commit body)
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5576
Co-authored-by: Tanmai Gopal <131160+coco98@users.noreply.github.com>
GitOrigin-RevId: 72c37f3e33a4483dcd12a6c1d7830a8c62d6185f
This removes string interpolation from quasiquoted literals. We only use
this in one place and it's totally unnecessary.
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5750
GitOrigin-RevId: 3493a11db6347332e7e3721a7dca616947505be6
## Description 🔖
This PR improves the DropdownButton API to make it more generic.
- It has been renamed Dropdown.
- The children are rendered as the trigger. You can now use other elements than a Button
- an option prop has been added to control all the radix ui element
- a group class name has been added to the trigger so you can style it based on its state, using tailwindcss-radix plugin
- stories of dropdown button as styled in the Hasura design system has been added
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5733
GitOrigin-RevId: 4d292ffcbec93ebae525764431e92b5ed87cb5b5
## Description 🔖
[VIDEO](https://www.loom.com/share/5844476e527f4e1d9ec296bc3a4bb932)
This PR creates a Tabs component that wraps the Radix UI component.
## Solution and Design 🎨
The component accepts all the props of the Radix UI tab root component and a list of items that specify the label and the content of the tabs. The component can be used in a controlled way (e.g., the state of the tab is stored in the URL) or uncontrolled.
For styling radix ui states I've added this library: https://github.com/ecklf/tailwindcss-radix
## Review Setup 💻
Run storybook and look for Tabs component
## Review checklist. 📋
- [ ] stories work
- [ ] doc is clear
PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5667
GitOrigin-RevId: 0e73ef1026d6673c3c2dd413b986fa8395abb1f6
