Skip to content

postgraphile@5.1.0

Choose a tag to compare

@github-actions github-actions released this 13 Jul 14:39
496a21b

Minor Changes

  • #3084
    dd3db66
    Thanks @benjie! - Add 'oid' as a builtin type.

  • #3098
    75444ac
    Thanks @benjie! - Fix: index behaviors plugin
    updated so that only attributes (columns) on tables, materialized views and
    foreign tables are scanned for indexes; all other types (including composite
    types, views, ...) are given the benefit of the doubt.

    This might result in more fields showing up in your schema.

  • #3081
    557791f
    Thanks @benjie! - V4 preset now supports @omit
    smart tags with spaces between values (e.g. @omit create, update, delete
    rather than @omit create,update,delete)

  • #3097
    b28eb75
    Thanks @benjie! - V4 preset now also grants
    +filterProc behavior when @filterable is present. Fixes compatibility with
    postgraphile-plugin-connection-filter.

  • #3090
    35d8b3e
    Thanks @benjie! - Bugfix: the V4 preset now
    correctly ignores @omit select like V4 would. Previously, the V4 preset
    would silently turn @omit select into -select, which differs to V4's
    handling of this. (Note: @omit read is probably what you're looking for,
    @omit select is silently ignored.)

  • #3060
    c21f24c
    Thanks @benjie! - makeSchema now awaits the
    writing of the SDL if enabled by exportSchemaSDLPath

Patch Changes

  • #3065
    9446f64
    Thanks @benjie! - fieldArgs are now created in
    the root plan and applied in the layer plan of the target step; this fixes an
    issue where fieldArgs could not be applied to step with side effects.

  • #3088
    d3d4376
    Thanks @benjie! - Add
    pgResource.extensions.isView, .isMaterializedView, .isForeignTable so
    plugins can determine which resources came from views/materialized
    views/foreign tables.

  • #3099
    4b5b673
    Thanks @benjie! - PostGraphile will only throw an
    error when it fails to read enum table values from a table in a published
    schema (one in the schemas list in your pgServices); enum tables in other
    schemas will result in a warning instead (since during the gather phase we
    don't know whether or not they will be needed come schema build time).

  • #3089
    24a9481
    Thanks @benjie! - Domain codecs can now indicate
    if they have a default value.

  • #3071
    3dff681
    Thanks @benjie! - Previously we used
    rootValue() to represent the Query type; but in GraphQL.js rootValue can be
    null/undefined. Typically you just need a truthy value, so we now use an empty
    object.

  • #3077
    5f95b1c
    Thanks @benjie! - CLIs will now correctly
    auto-import graphile.config.mts files (previously graphile.config.ts files
    worked, but graphile.config.mts files would be ignored). With all major
    versions of Node.js now having native support for type stripping and
    require(esm), we recommend moving your configuration files to TypeScript
    (using ESM and erasable syntax only).

  • #3078
    00bb2ba
    Thanks @evolkmann! - Export types related to
    the pgSmartTags/etc utils (PgSmartTagRule, PgSmartTagTags,
    PgSmartTagFilterFunction, JSONPgSmartTags, etc.).

  • #3083
    3cbbd88
    Thanks @benjie! - Add safer assumptions to
    @omit behavior fallback

  • Updated dependencies
    [9446f64,
    dd3db66,
    d3d4376,
    d5fa38b,
    56f8add,
    1a9b835,
    ccbbd7c,
    65527f8,
    3b56a51,
    e60e2ed,
    79b234e,
    f0d1f48,
    4b5b673,
    75444ac,
    24a9481,
    3dff681,
    350dd8d,
    8b3904d,
    d3156df,
    5f95b1c,
    00bb2ba,
    c21f24c]:

    • graphile-build-pg@5.1.0
    • grafast@1.1.0
    • @dataplan/pg@1.1.0
    • @dataplan/json@1.0.1
    • grafserv@1.0.1
    • graphile-build@5.1.0
    • graphile-config@1.1.0
    • graphile-utils@5.0.2