fix: Migrate API usage from *.metafi & *.metaswap subdomains to *.cx.metamask.io"#4301
Conversation
mikesposito
left a comment
There was a problem hiding this comment.
Looks good! Just a small question
|
These changes should be transparent for external consumers, since the old endpoints should be functionally equivalent to the new ones - so I don't think we should mark them as breaking. Or do you expect something to break? |
Yes I agree in somehow this should not be tagged as breaking change but in similar change this was marked as |
|
@cryptodev-2s Hmm, I am not sure why they marked the changes as breaking in that PR. That seems like a mistake to me. I had the same understanding as @mikesposito, that the new URL is simply an alias for the old one. I also agree that we should not mark these as breaking. |
mcmire
left a comment
There was a problem hiding this comment.
I've cross-referenced these URL changes via Slack and they look correct to me.
Explanation
API Platform team intends to deprecate *.metafi and *.metaswap subdomains in favour of *.api.cx.metamask.io
The new *.api.cx.metamask.io is already in place.
The old *.metafi and *.metaswap are still used across the controllers.
Controllers do not break currently because redirects are in place for the older sub-domains.
The redirects will be removed once all clients (Extension, Mobile, Core) are migrated.
References
Changelog
@metamask/assets-controllerprice-api.metafi.codefi.networktoprice.api.cx.metamask.io*.metafi.codefi.networkto*.cx.metamask.iotoken-api.metaswap.codefi.networktotoken.api.cx.metamask.io@metamask/phishing-controller*.metafi.codefi.networkto*.api.cx.metamask.io@metamask/controller-utils*.metafi.codefi.networkto*.api.cx.metamask.io@metamask/name-controllertoken-api.metaswap.codefi.networktotoken.api.cx.metamask.ioChecklist