Right now query in the nodejs api is just a string. we should support gql-parsed strings too, so that if they are exported elsewhere, it can be used directly.

import gql from 'graphql-tag';

export const GRAPHQL_QUERY=gql`
  query {
    something {
      anotherthing
    }
  }
`;

I'm not sure how feasible this may be, but the old logparser program from Microsoft supported queries like

Select * from test.csv

And it would read from test.csv, without needing any config files.

Currently pgTyped CLI package is using minimist for CLI flag parsing. By design minimist is rather minimal and doesnt provide any advanced features.

To improve the current CLI experience we should switch to yargs.

Things we will get out of the box with yargs:

• Help command
• Env variable support
• Flag value validation
• Documented default values

One issue that's kept me from adopting this gem more widely is that I need to define all possible top level keys for a jsonb column. If I don't, then I will receive an ActiveRecord::MissingAttributeError. This removes much of the flexibility of having a jsonb column. For example when storing a JSON response from a webhook. The structure may be well defined, but if a new key is added then we'd ge

Hi,
I was using this amazing package on my project.
I have requirement to modify cache content directly, in parralel with the update of database. So I could prevent re query everytime. So I need to get the key of a cache.

I'm using newest version and using redis as my cache driver

After making some debug into redis every key looks like prefixed with string like this
my_project_database_my

Tools like jq are focused predominantly on their use on the command line, but have a lot of limitations (and bugs!) that jslt doesn't. This is a compliment to jslt btw. :)

To properly replace the usage of jq with jslt, we would like to be able to have some more flexibility with the ways of specifying the input parameters as well as the output.

• Specifying JSON input or JSLT transform input