-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Support Exotic rarity #367
Conversation
src/ports/orders/utils.ts
Outdated
@@ -210,7 +210,7 @@ export const getOrdersQuery = ( | |||
|
|||
export function fromOrderFragment( | |||
fragment: OrderFragment, | |||
network: Network, | |||
network: Network.MATIC | Network.ETHEREUM, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cant we use AssetsNetwork here too?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done!
fromItemFragment(fragment, network, chainId) | ||
fromItemFragment( | ||
fragment, | ||
network as Network.ETHEREUM | Network.MATIC, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this necessary? fromItemFragment is receiving AssetsNetwork too
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This network
variable comes from the ItemFilters
, which is still using the Rarity
type. As changing it might impact multiple projects, I chose casting it here, but I made sure that we were getting one or the other when receiving the query parameters.
This PR changes the NFT server to support the exotic rarity.