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
[x] Regression
[ ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.
Current behavior
It returns the id instead of the the relayId
Expected behavior
It should return the relayId
Minimal reproduction of the problem with instructions
Check out this repo bug/v7
Then run npm run test:integration --testPathPattern code-first.spec.ts$
What is the motivation / use case for changing the behavior?
Want to map internal id to relay's global id
Environment
Nest version: 7
For Tooling issues:
- Node version: 13.9.0
- Platform: Linux
Others:
The text was updated successfully, but these errors were encountered:
leesiongchan
changed the title
[v7] name alias will directly lookup to the property instead of the getter function
[v7] name alias will lookup directly to the property instead of the getter function
Mar 17, 2020
leesiongchan
changed the title
[v7] name alias will lookup directly to the property instead of the getter function
[v7] name will lookup directly to the property instead of the getter function
Mar 17, 2020
I'm submitting a...
Current behavior
It returns the
id
instead of the therelayId
Expected behavior
It should return the
relayId
Minimal reproduction of the problem with instructions
Check out this repo bug/v7
Then run
npm run test:integration --testPathPattern code-first.spec.ts$
And here is the commit
What is the motivation / use case for changing the behavior?
Want to map internal id to relay's global id
Environment
The text was updated successfully, but these errors were encountered: