Building Queries #765
Replies: 50 comments
|
💬 avior on Discord wrote: any fields from the card should work |
|
💬 tishingo on Discord wrote: how do some of the nested fields work in that case? |
|
💬 avior on Discord wrote: the API do a non deep search on the subfields |
|
💬 avior on Discord wrote: you can't currently do legal comparaison currently |
|
💬 tishingo on Discord wrote: okay thats fine, i can make it up with the sets. |
|
💬 avior on Discord wrote: this is something that will be added later |
|
💬 tishingo on Discord wrote: i see regulationMark is toplevel, but i get 500 errors when i try searching that way, is that not available either? |
|
💬 avior on Discord wrote: 5xx errors should not happens xd |
|
💬 avior on Discord wrote: that is something on our end |
|
💬 avior on Discord wrote: i'm looking into what's happening |
|
💬 tishingo on Discord wrote: i appreciate it. that would be an easier approach to figuring out the standard legal set on my end |
|
💬 avior on Discord wrote: The error was found ! |
|
💬 avior on Discord wrote: I'm releasing an pdate with it |
|
💬 avior on Discord wrote: i'll reverve my changes on the server |
|
💬 avior on Discord wrote: and as it's quite late I'll look into it this morning (it's 3AM where I live) |
|
💬 avior on Discord wrote: thanks for your understanding ! |
|
💬 tishingo on Discord wrote: thanks i appreciate it |
|
💬 tishingo on Discord wrote: just as a mental note for you, it looks like the changes were reverted and the calls are working again (minus the new ones obv) |
|
💬 avior on Discord wrote: Hey, so it seems that I can't replicate the error 😦 I pushed again the update and added error monitoring at another level so it should catch it in the production build, I also changed how my responses were cached and 400+ errors were cached before 😦 but now they aren't 🙂 |
|
💬 tishingo on Discord wrote: maybe it was a deployment fluke? |
|
💬 tishingo on Discord wrote: so is it working now? |
|
💬 tishingo on Discord wrote: Looks like it is. |
|
💬 tishingo on Discord wrote: For anyone who stumbles on this thread, here was my solution for building queries in javascript: I made it so the filterParams are passed as an object. a more advanced example would just add additional fields to the object: |
|
💬 cssagogo on Discord wrote: What would acceptable values for Weaknessess be? |
|
💬 cssagogo on Discord wrote: I've tried various methods, but they all seem to return a blank array: |
|
💬 avior on Discord wrote: I'll take a look at it, the filtering system need some tweaks |
|
If I run the query through a 'legal.standard' URL parameter it works… but I can't get it to work using the SDK queries: query.equal('legal.standard', 'true'); |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
💬 tishingo on Discord wrote:
I was trying to query regulation marks earlier but It was failing in postman
All reactions