hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-19 13:31:43 +03:00
Code Issues Projects Releases Wiki Activity
0361158ab7
graphql-engine/server/lib/aeson-ordered/aeson-ordered.cabal

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

73 lines
2.0 KiB
Plaintext
Raw Normal View History

server: fix cabal files; apply ghc warnings more strictly - In a previous PR we made more use of `common` stanzas, but these require `cabal-version: 2.2` (so some of those stanzas were not functional before this PR). This just bumps the `cabal-version`s straight to 3.6, which is the latest version we support in CI, where we build with cabal 3.6. - This `cabal-version` upgrade required fixing a few `license` fields, from `BSD3` to `BSD-3-Clause`. I've also added `default-language` fields where appropriate, although this is perhaps optional. - Using cabal's [syntax for applying options to all _local_ packages](https://cabal.readthedocs.io/en/3.8/cabal-project.html#package-configuration-options), we unify the cabal configuration, and apply `-Werror` to all local packages, which wasn't the case until now. - Applying `-Werror` to all local packages required a few additional exceptions to the warnings that were switched on in hasura/graphql-engine-mono#7614. - Deleted SCM links to the original pool library. Overall, the effect of this PR is: - more warnings - stricter compilation - ~~less cabal configuration~~ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7730 GitOrigin-RevId: 592e9e46d103bcc8726df5b745306bd9f77f7efc
2023-01-31 21:23:52 +03:00
cabal-version: 3.6
server: move ordered Aeson into its own package PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4939 GitOrigin-RevId: 62e83ae7c69f4e0a5334cf1e0c85c22a5d378f59
2022-07-07 18:54:32 +03:00
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
name: aeson-ordered
version: 0.1.0.0
description: Provides a data type that mirrors Aeson's 'Value', but that preserves order of object properties using an insertion-ordered map.
homepage: https://github.com/hasura/github-engine-mono#readme
bug-reports: https://github.com/hasura/github-engine-mono/issues
author: Anon Ray <anon@hasura.io>,
Bryan O'Sullivan <bos@serpentine.com>,
MailRank, Inc.
maintainer: Anon Ray <anon@hasura.io>,
Bryan O'Sullivan <bos@serpentine.com>,
MailRank, Inc.
server: fix cabal files; apply ghc warnings more strictly - In a previous PR we made more use of `common` stanzas, but these require `cabal-version: 2.2` (so some of those stanzas were not functional before this PR). This just bumps the `cabal-version`s straight to 3.6, which is the latest version we support in CI, where we build with cabal 3.6. - This `cabal-version` upgrade required fixing a few `license` fields, from `BSD3` to `BSD-3-Clause`. I've also added `default-language` fields where appropriate, although this is perhaps optional. - Using cabal's [syntax for applying options to all _local_ packages](https://cabal.readthedocs.io/en/3.8/cabal-project.html#package-configuration-options), we unify the cabal configuration, and apply `-Werror` to all local packages, which wasn't the case until now. - Applying `-Werror` to all local packages required a few additional exceptions to the warnings that were switched on in hasura/graphql-engine-mono#7614. - Deleted SCM links to the original pool library. Overall, the effect of this PR is: - more warnings - stricter compilation - ~~less cabal configuration~~ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7730 GitOrigin-RevId: 592e9e46d103bcc8726df5b745306bd9f77f7efc
2023-01-31 21:23:52 +03:00
license: BSD-3-Clause
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
license-file: LICENSE
build-type: Simple
server: move ordered Aeson into its own package PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4939 GitOrigin-RevId: 62e83ae7c69f4e0a5334cf1e0c85c22a5d378f59
2022-07-07 18:54:32 +03:00
extra-source-files:
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
CHANGELOG.md
LICENSE
server: move ordered Aeson into its own package PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4939 GitOrigin-RevId: 62e83ae7c69f4e0a5334cf1e0c85c22a5d378f59
2022-07-07 18:54:32 +03:00
source-repository head
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
type: git
location: https://github.com/hasura/github-engine-mono
server: move ordered Aeson into its own package PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4939 GitOrigin-RevId: 62e83ae7c69f4e0a5334cf1e0c85c22a5d378f59
2022-07-07 18:54:32 +03:00
library
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
exposed-modules:
Data.Aeson.Ordered
other-modules:
Paths_aeson_ordered
hs-source-dirs:
src
default-extensions:
BangPatterns
DeriveDataTypeable
DeriveGeneric
DerivingStrategies
GeneralizedNewtypeDeriving
ImportQualifiedPost
LambdaCase
OverloadedStrings
StrictData
server: enable all the warnings (that we can) See [Enable all the warnings](https://medium.com/mercury-bank/enable-all-the-warnings-a0517bc081c3). This PR follows that approach, except that it re-disables those warnings that would prevent a successful build. There are some newer warning flags that older GHC versions don't recognize. So this also updates some of our CI routines to the GHC version that we're currently using for `graphql-engine` itself, namely 9.2.5. I don't see a reason to keep testing those libraries against older GHC versions. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7614 GitOrigin-RevId: d48a6db09dab29616e273549d0045f98ecb4586f
2023-01-30 14:23:08 +03:00
ghc-options:
-foptimal-applicative-do
-- Taken from https://medium.com/mercury-bank/enable-all-the-warnings-a0517bc081c3
-Weverything
-Wno-missing-exported-signatures
-Wno-missing-import-lists
-Wno-missed-specialisations
-Wno-all-missed-specialisations
-Wno-unsafe
-Wno-safe
-Wno-missing-local-signatures
-Wno-monomorphism-restriction
-Wno-missing-kind-signatures
-Wno-missing-safe-haskell-mode
-- We want these warnings, but the code doesn't satisfy them yet:
-Wno-missing-deriving-strategies
server: fix cabal files; apply ghc warnings more strictly - In a previous PR we made more use of `common` stanzas, but these require `cabal-version: 2.2` (so some of those stanzas were not functional before this PR). This just bumps the `cabal-version`s straight to 3.6, which is the latest version we support in CI, where we build with cabal 3.6. - This `cabal-version` upgrade required fixing a few `license` fields, from `BSD3` to `BSD-3-Clause`. I've also added `default-language` fields where appropriate, although this is perhaps optional. - Using cabal's [syntax for applying options to all _local_ packages](https://cabal.readthedocs.io/en/3.8/cabal-project.html#package-configuration-options), we unify the cabal configuration, and apply `-Werror` to all local packages, which wasn't the case until now. - Applying `-Werror` to all local packages required a few additional exceptions to the warnings that were switched on in hasura/graphql-engine-mono#7614. - Deleted SCM links to the original pool library. Overall, the effect of this PR is: - more warnings - stricter compilation - ~~less cabal configuration~~ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7730 GitOrigin-RevId: 592e9e46d103bcc8726df5b745306bd9f77f7efc
2023-01-31 21:23:52 +03:00
-Wno-deriving-typeable
-Wno-implicit-prelude
server: Automate generation and verification of Cabal files from hpack. We currently use `hpack` to generate the Cabal files from _package.yaml_ files for the two small libraries in _server/lib_. While this is more convenient, we also check the Cabal files into the repository to avoid needing an extra step upon pulling changes. In order to ensure that the Cabal files do not get out of sync with the hpack files, this introduces a few improvements: 1. Makefile targets to automatically generate the Cabal files without needing to know the correct incantation. These targets are a dependency of all build targets, so you can simply run `make build-all` and it will work. 2. An extra comment at the top of all generated Cabal files that explains how to regenerate it. 3. A `lint-hpack` Makefile target that verifies that the Cabal files are up-to-date. 4. A CI job that runs `make lint-hpack`, to stop inconsistencies getting merged into trunk. Most of these changes are ported from #4794. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/5217 GitOrigin-RevId: d3dfbe19ec00528368d357b6d0215a7ba4062f68
2022-07-29 19:21:00 +03:00
build-depends:
aeson
, attoparsec
, base
, bytestring
, hashable
, insert-ordered-containers
, lens
, lens-aeson
, scientific
, text
, vector
default-language: Haskell2010
Reference in New Issue Copy Permalink