Skip to main content Link Search Menu Expand Document (external link)

Inigo v0.14.0

September 14, 2022

Enhancements

  • Explore
    • We added ability to group by user.
    • We added ability to filter by query path.
  • Home
    • We added a new widget for queries which consume the most credits.
  • Access Control
    • We added ability to configure access rules in the schema using the @access directive.
  • Rate Limit
    • We added support to control rate limit differently for each root field of queries or mutations. With this configuration one can disable rate limit for specific queries or have different queries consume different amount of credits.
  • Observe
    • We added ability to tag fields in the schema which can then be viewed in the tree view explore page. Directives such as @sensative, @restricted or any other custom directive can be configured on different fields, and then be seen via different filters in the explore ui.
    • We added a knob to enable a deprecation warning extension to be appended to all operations that use deprecated fields.
  • Security
    • We added security controls for max_root_queries and max_root_mutations to be able to limit the number of batched queries allowed.
    • We added a way to require particular fields to be present in a given type using the require_fields configuration.
    • We added a way to require ID fields to always be present in queries using the require_id_fields configuration.
  • Miscellaneous
    • We added ability to reduct data from the operation response extensions. This feature can be used to make sure stack traces or debug info is never sent back to the client.
    • We added ability to apply configuration for the Starwars demo directly from the ui.
    • We enhanced our hosted Starwars demo to also be able to point to any remote GraphQL endpoint. You can now try a hosted demo version of Inigo with your own api without needing to deploy anything.

Migration

  • In v0.13.0 configurations with value of 0 were used to signify the particular knob or configuration was disabled or unused. Starting in v0.14.0 null is used to signify disabled configurations. To migrate over to v0.14.0 all knobs which were set to zero should be set to null or completely removed. Reapply your configuration for the migration to take place using ‘inigo apply’.

Bug Fixes

  • Fixed explore table pagination