-
Notifications
You must be signed in to change notification settings - Fork 476
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
Shopify API deprecations warning on order resource #1187
Comments
I am getting this too |
@mattsrobot were you able to resolve this? or maybe find a workaround for this? |
I'm also still seeing this, and it's just coming from a pretty simple call to:
Presumably |
Does anybody found a solution? |
Anyway it doesn't seems to be related to the gem.
Output:
As you can see I received only But it keeps complaining that I am using deprecated API calls: |
Getting the same issue just FYI & it's March 2024, doesnt seem to have been addressed... |
I am going to close this issue. As @link82 pointed out this is not related to the gem specifically. If you make an API call to a REST resource with deprecated fields, it will return to you a warning about the deprecated fields. If you are not using those fields then you can ignore the message. |
Personally I don't think that's a satisfactory result - on a sufficiently-sized codebase it results in way too many false-negatives. It would be far better to throw these deprecation errors from attribute getters, rather than just an API call that included them. It essentially makes deprecation errors absolutely useless - can we ignore them? Can't we? Who knows! |
Hey @jaspertandy I think that is very fair feedback. I have brought this up with the API team, to resolve this at the API level, the API shouldn't return warnings if you are not affected but at this time I have no updates to pass along. We don't really have a good way to solve this at the gem level at this time. As a we don't know what fields are deprecated. We would need to get that information into the library first. I will reflag with the product team about getting that information into the library, as this is something we have discussed in the past. |
Completely understand @lizkenyon - I wasn't expecting an immediate solution and I know it's not a simple problem (otherwise Shopify probably would have done it long ago!). I also appreciate that it's not a very glamourous problem to work on, but I do appreciate you and the team reconsidering it. On another service it wouldn't be such a problem but Shopify's API moves very quickly and we need to be able to trust and react to those deprecations so we don't get stung by them! |
Issue summary
shopify_api
version: 2022-10Expected behavior
No Deprecation warnings upon requesting order resources
Actual behavior
https://shopify.dev/changelog/property-deprecations-in-the-admin-api-order-and-lineitem-resource
But when I go to https://shopify.dev/changelog/property-deprecations-in-the-admin-api-order-and-lineitem-resource I'm not using any of the attributes here.
I'm guessing/hoping this is to do with the API wrapper itself requesting these fields when it sets data from the API, and triggering its own deprecations but it would be good to get confirmation of that as it's super confusing.
The text was updated successfully, but these errors were encountered: