You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just started playing around with the API - from the closed issues and the responses I get I understand you're anonymising a lot of data. Understandable.
I wondered if this was documented anywhere more verbosely than what's in iQL?
Am I right in my understanding that fields like makers in post will now be an array of 0 for the id unless I am one of the makers (and therefore my id would be in scope for the request)?
Running this query:
query test {
post(id: "382374") {
comments (first: 1) {
nodes {
url
user {
isMaker
}
userId
}
}
name
url
makers {
id
}
}
}
The response gives me 0's for the makers - fine, I guess.
My problem is that the isMaker flag under the user in the comments nodes is false, when in reality it is true - would it be possible to use a more explicit state such as null rather than mislead?
And is the redaction a continuous work in progress? Or is the API currently stable?
Thanks!
The text was updated successfully, but these errors were encountered:
HI!
Just started playing around with the API - from the closed issues and the responses I get I understand you're anonymising a lot of data. Understandable.
I wondered if this was documented anywhere more verbosely than what's in iQL?
Am I right in my understanding that fields like
makers
inpost
will now be an array of0
for theid
unless I am one of themakers
(and therefore myid
would be in scope for the request)?Running this query:
The response gives me
0
's for the makers - fine, I guess.My problem is that the
isMaker
flag under theuser
in thecomments
nodes isfalse
, when in reality it istrue
- would it be possible to use a more explicit state such asnull
rather than mislead?And is the redaction a continuous work in progress? Or is the API currently stable?
Thanks!
The text was updated successfully, but these errors were encountered: