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
{{ message }}
This repository has been archived by the owner on May 26, 2022. It is now read-only.
I used an alias in my graphql query but all the react queries failed
because the sorting has to contain the original name not the alias.
Not sure if that's an issue with react passing the order by as a parameter, I think rather that neo4j-graphql-js should take the alias into account.
changes I had to make (from "name" to display_name
functionUserList(props){const{ classes }=propsconst[order,setOrder]=React.useState('asc')const[orderBy,setOrderBy]=React.useState('display_name')// <- here
<TableCellkey="name"sortDirection={orderBy==='name' ? order : false}><Tooltiptitle="Sort"placement="bottom-start"enterDelay={300}><TableSortLabelactive={orderBy==='name'}direction={order}onClick={()=>handleSortRequest('display_name')}<!--here-->>Name</TableSortLabel></Tooltip></TableCell>
this makes it kinda inconsistent and hard to reason about.
##Also Error Handling
When the errors occurred I only saw Error in the UI, no error message, not even in chrome debug tools
I had to run the query with the params from the react app manually against the graphql api to see the error message
it was also no error output in the terminal of api or web-react, even as it was running in dev-mode.
And no "errors" response data, but an HTTP 400
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I used an alias in my graphql query but all the react queries failed
because the sorting has to contain the original name not the alias.
Not sure if that's an issue with react passing the order by as a parameter, I think rather that neo4j-graphql-js should take the alias into account.
changes I had to make (from "name" to
display_name
this makes it kinda inconsistent and hard to reason about.
##Also Error Handling
When the errors occurred I only saw
Error
in the UI, no error message, not even in chrome debug toolsI had to run the query with the params from the react app manually against the graphql api to see the error message
it was also no error output in the terminal of
api
orweb-react
, even as it was running in dev-mode.And no "errors" response data, but an HTTP 400
The text was updated successfully, but these errors were encountered: