lefortov / react-two-way-querybuilder Goto Github PK

Use query config as (firstname= 'jhon'), It gives an error for undefined value at line 73 in Query parser.js. I managed it working by replacing the line with if (element.value && element.value.field)

I'd like to integrate this awesome package in a wrapper for uniforms, but the button ADD RULE is of type submit by default and it triggers submit event to whole form when clicked. The rest of the buttons don't have such behavior. Did I miss something? Can anyone, please, help me with this issue?

I am trying to pass multiple options in config (query, combinators and operators) but only one at a time is working. Can anyone tell me how to customise query builder by passing all the config together? Or this is a bug?

Seems as though its having trouble building the filter from a saved query

Now when I try and use a saved query to load with config={ query: ( name='Bob' AND whatever= 'whatever')} I get :
Rule.js:170 Uncaught TypeError: Cannot read property 'input' of undefined

Query builder works fine when I include it in my project, but creating a new build fails. It points to invalid CSS in styles.css. Seems like the issue is with this particular line.

background-image: url(data:image/svg+xml,%3Csvg%20width%3D%2210px%22%20height%3D%225px%22%20viewB…oints%3D%227%2010%2012%2015%2017%2010%22%3E%3C%2Fpolygon%3E%0A%3C%2Fsvg%3E);

for eg :
let config = {

             query : "(SandraUser EQUALS 'Jack' AND BobName EQUALS 'London')" }

The UI does not get built properly for the query. The field for name does not get initialized properly. It always selects the first name in the list.

The operators and the custom text field work fine. Only a problem with getting the right name.

It should be really selecting this for that filter :

The problem is in displaying the name. it builds the text query into the dict query correctly.

Your demo for existing query seems to be correct but if you try and load an existing query that has select dropdown , or uses any operator other than '=' is gets messed up.
Example if i set a query like this:

The query looks like this:

(name = ' Fred' AND offices IN 'Oakland')

But if I try and Load that query in

config = { query: "(name = ' Fred' AND offices IN 'Oakland')" }

it builds the query UI messed up

Offices isn't selected and its operator is incorrect and the N from IN operator is added to value and value is cut off?Also noticed extra space it added...

Any insight?
Does that token creator function need some refactoring maybe

Dear Team,

I have a small scenario, I am using the tool with the Input type as "Select" for value selection. When I reload the query the values select is always showing the first value not the exact value from the query. Although select also contains the values that are in the query value.

e.g. In the Select input contains: [{name: 100, value: 100}, {name: 101, value: 101}]
Query: '((leftValue >= 101 AND rightValue < 101) OR leftValue = 101)'
but when I old the query all other things are fine, but values are always 100 although query contains 101.

Any idea?

Thanks in Advance

Hey great module.

I am trying this out and am trying to have specific operators per field but that seems to crash my app unless i only have it set as ... operators: 'all' ...

i have tried

...
{name: 'name', label: 'Account Name', input: { type: 'text' },operators: [ { operator: '=', label: '=' },{ operator: '<>', label: '<>' }] } ,
...

AND as per read me

...
{name: 'name', label: 'Account Name', input: { type: 'text' },operators: [  '=',  '<>'] } ,
...