refactor: NFT GraphQL Integration

[cbachmeier]

Your PR title must follow conventional commits, and should start with one of the following types:

• build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
• ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
• docs: Documentation only changes
• feat: A new feature
• fix: A bug fix
• perf: A code change that improves performance
• refactor: A code change that neither fixes a bug nor adds a feature
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
• test: Adding missing tests or correcting existing tests

Example commit messages:

• feat: adds support for gnosis safe wallet
• fix: removes a polling memory leak
• chore: bumps redux version

Other things to note:

• Please describe the change using verb statements (ex: Removes X from Y)
• PRs with multiple changes should use a list of verb statements
• Add any relevant unit / integration tests
• Changes will be previewable via vercel. Non-obvious changes should include instructions for how to reproduce them

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
interface	✅ Ready (Inspect)	Visit Preview	Oct 27, 2022 at 5:21AM (UTC)

[gbugyis]

I'm seeing a lot of browser console warnings like these Warning: RelayResponseNormalizer: Invalid record. The record contains two instances of the same id: 'TmZ0Q29ud...' with conflicting field, standard and its values: ERC721 and null. If two fields are different but share the same id, one field will overwrite the other.

[cbachmeier]

Worked with back end and updated where we retrieve the token standard to fix logging errors