hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 17:02:49 +03:00
Code Issues Projects Releases Wiki Activity
07452e6067
graphql-engine/v3/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

48 lines
1.1 KiB
TOML
Raw Normal View History

v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
[workspace]
resolver = "2"
Set the crate properties once, to improve the Nix build. (#334) V3_GIT_ORIGIN_REV_ID: ec5f3d968306a64ad5c63df324ca5c524838c598
2024-03-06 20:14:24 +03:00
package.version = "0.1.0"
package.edition = "2021"
package.license = "Apache-2.0"
v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
members = [
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/auth/*",
"crates/custom-connector",
"crates/engine",
Split out `execute` crate (#588) <!-- Thank you for submitting this PR! :) --> ## Description Following `metadata-resolve` and `schema` crates, this splits out `execute`, the largest folder in `engine`. Undoubtedly this could be split further. Functional no-op. V3_GIT_ORIGIN_REV_ID: c272908153f78212d1f5dd58819707ac3cbcd439
2024-05-17 17:41:32 +03:00
"crates/execute",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/lang-graphql",
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
"crates/metadata-resolve",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/metadata-schema-generator",
"crates/open-dds",
data shape for query usage analytics (#606) ## Description The expectation is, that engine should emit usages of OpenDD objects (i.e. models, commands, relationships, permissions, fields of types etc.) from a GraphQL query. This PR adds the types required to gather query usage analytics, under a new crate `query-usage-analytics`. V3_GIT_ORIGIN_REV_ID: 49778c25a9019e0c8c9a2d13eaa8ba28638b8b55
2024-05-28 12:50:21 +03:00
"crates/query-usage-analytics",
Split `schema` into own crate (#556) <!-- Thank you for submitting this PR! :) --> ## Description This PR splits the GraphQL schema generation into the `schema` crate. Functional no-op. V3_GIT_ORIGIN_REV_ID: 4f1a91387305d88e9b5fbe4bc8df0575292cf878
2024-05-08 15:04:39 +03:00
"crates/schema",
create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) ## Description 1. I've moved the architecture information we had in `CONTRIBUTING.md` to a separate document `docs/architecture.md` so we can evolve both separately in the future. 2. I've introduced a couple of sub directories: `utils` and `auth`, for supporting crates that are not the core functionality of the engine so it is easier to find the most relevant crates. New structure: ``` crates ├── auth │   ├── dev-auth-webhook │   ├── hasura-authn-core │   ├── hasura-authn-jwt │   └── hasura-authn-webhook ├── custom-connector ├── engine ├── lang-graphql ├── metadata-schema-generator ├── open-dds └── utils ├── opendds-derive ├── recursion_limit_macro └── tracing-util ``` V3_GIT_ORIGIN_REV_ID: e0e9394da2fcd911f329c48107a76f8492fa304c
2024-05-01 12:04:24 +03:00
"crates/utils/*",
v3: open-source hasura v3 engine Hasura V3 Engine v3.alpha.12-19-2023 V3-GitOrigin-RevId: 6605575a52b347b5e9a14ecd1cc736f113c663b3 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/10567 Co-authored-by: Vishnu Bharathi <4211715+scriptnull@users.noreply.github.com> GitOrigin-RevId: 38c98a4b1971efe3ac724c2371c43ceb7d31f140
2023-12-19 12:04:02 +03:00
]
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
[workspace.lints.clippy]
all = { level = "warn", priority = -1 }
pedantic = { level = "warn", priority = -1 }
# disable certain pedantic warnings
doc_markdown = "allow"
Semicolons, everywhere! (#700) If a function doesn't return a value, terminate with a semicolon. I also moved `implicit_hasher` and `return_self_not_must_use` to the "definitely keep disabling this" list, and installed [Bacon](https://dystroy.org/bacon/) in the Nix shell to make it easier to run Clippy. V3_GIT_ORIGIN_REV_ID: ffb17b42d982518aec433a1676dba0a0dd0ad95d
2024-06-11 18:32:43 +03:00
implicit_hasher = "allow"
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
missing_errors_doc = "allow"
missing_panics_doc = "allow"
module_name_repetitions = "allow"
must_use_candidate = "allow"
Semicolons, everywhere! (#700) If a function doesn't return a value, terminate with a semicolon. I also moved `implicit_hasher` and `return_self_not_must_use` to the "definitely keep disabling this" list, and installed [Bacon](https://dystroy.org/bacon/) in the Nix shell to make it easier to run Clippy. V3_GIT_ORIGIN_REV_ID: ffb17b42d982518aec433a1676dba0a0dd0ad95d
2024-06-11 18:32:43 +03:00
return_self_not_must_use = "allow"
Apply a few lints to make it struct construction clearer. (#661) 1. Always name the struct when calling `default()`. 2. Sort construction according to the definitions. 3. Approve allowing `struct_field_names` because it doesn't seem to be helpful. 4. Enable `manual_string_new`; nothing seems to be triggering it now. V3_GIT_ORIGIN_REV_ID: 868742114b0bf27bc3ea03cdf1e63a0f710ebe33
2024-06-04 11:42:01 +03:00
struct_field_names = "allow"
use clippy settings in Cargo workspace (#441) <!-- Thank you for submitting this PR! :) --> ## Description Following the approach taken here: https://github.com/hasura/ndc-postgres/pull/402 This moves the `clippy` settings into the Cargo workspace file instead of passing them for each invocation. We enable all pedantic settings, run `cargo clippy --fix` to auto fix a few things, and then manually disable all other lints. Plenty of them are worth enabling and fixing in future IMO. --------- Co-authored-by: Samir Talwar <samir.talwar@hasura.io> V3_GIT_ORIGIN_REV_ID: aa0e6ccb8d72a7393e14b5c58b82077a67d9cb15
2024-04-08 13:13:26 +03:00
wildcard_imports = "allow"
# disable these for now, but we should probably fix them
result_large_err = "allow"
similar_names = "allow"
too_many_arguments = "allow"
too_many_lines = "allow"
unnecessary_box_returns = "allow"
unnecessary_wraps = "allow"
unreadable_literal = "allow"
unused_async = "allow"
used_underscore_binding = "allow"
fix cargo doc warnings (#585) ## Description As advertised. Now you can run the following to browse our internal code ``` cargo doc --no-deps --document-private-items --open ``` V3_GIT_ORIGIN_REV_ID: 5b7091a00ed6148b8a91168807b07aa6a925cac9
2024-05-16 12:04:07 +03:00
[workspace.lints.rustdoc]
private_intra_doc_links = "allow"
Reference in New Issue Copy Permalink