We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now the workflow, wrt adding the queries to the dynatable object seems to be .
dynatable.queries.add("key1", value1); dynatable.queries.add("key2", value2);
if in the UI , the key2 field was removed, the query entry would also have to be removed before calling dynatable.process. so, rather than calling
dynatable.queries.remove("key1") and // calling remove on all fields,
there should be something like
dynatable.queries.clear() // This sets the queries to a fresh initial state
The text was updated successfully, but these errors were encountered:
Good point. I'll leave this open and add this to the queue.
Sorry, something went wrong.
I can help with this if you'd like
--gp
On Tue, Feb 25, 2014 at 1:15 AM, Steve Schwartz [email protected]:
Good point. I'll leave this open and add this to the queue. Reply to this email directly or view it on GitHubhttps://github.com//issues/67#issuecomment-35926972 .
Reply to this email directly or view it on GitHubhttps://github.com//issues/67#issuecomment-35926972 .
fix alfajango#67 | provide a way to clear the queries array
cfa4bdf
No branches or pull requests
Right now the workflow, wrt adding the queries to the dynatable object seems to be .
if in the UI , the key2 field was removed, the query entry would also have to be removed before calling dynatable.process.
so, rather than calling
there should be something like
The text was updated successfully, but these errors were encountered: