query

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.

I'd like to add a config and the ability to have a .js config file in order to generate nestjs repositories and files that just have types. The easiest way to do this, and without introducing much additional maintenance would be to let folks supply their own generator templates.

Splitting the types to a different library might be a little tricky to add in a config, so at first it might not b

Describe the bug
I created a component in QueryBuilder.tsx by taking the example from the README with some little cleanup. It all worked except the CSS import causes an issue. Is there a solution that is supported in tsx or a hosted css file that can be used?

./node_modules/react-awesome-query-builder/lib/css/styles.css:1
.qb-drag-handler, .qb-draggable, .query-builder {
^

Synt

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

Note sure if it could be interesting but:

When registering a table:

addr: 0.0.0.0:8084
tables:
  - name: "example"
    uri: "/data/"
    option:
      format: "parquet"
      use_memory_table: false

add in options:
glob

pattern: "file_typev1*.parquet"

or regexp

pattern: "\wfile_type\wv1\w*.parquet"

It would allow selecting in uri's with different exte

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