Refactor Subgraph NFT using composition #527
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In the current implementation the GNS was turned into a NFT registry by adding the related state variables and behaviours through an upgrade. The upgrade is not yet done in mainnet. While testing in Rinkeby the team identified that some platforms (OpenSea, Etherscan, Rarible, etc.) couldn't properly identify a contract that was previously deployed as a non-NFT that was upgraded to be an NFT registry. That means that they won't display the NFT metadata properly.
The original implementation was done in the following PR: #497
Solution
Use composition instead of inheritance to add the NFT functionality.