Migrate missing features and fixes from old SDK

[butenkor]

Topic for discussion

It is pity that we hit same issues with new SDK which has been addressed in old SDK already as for existing customers migration might be a costly enterprise as they might hit issues that were not present with old SDK. The reason is obviously that rewrite of new SDK was based on old SDK and as it took around 1 year of development all the fixes/features applied to old SDK during that time were not migrated to the new SDK release.

Suggestion

Review all issues/PRs/commits from old SDK implemented after rewrite fork and create a list of TODOs for migration like examples below.

Missing fixes/features

• - Sync actions should first remove variants
• - fetch all convenience function for multi-paged results
• - GraphQL convenience method which allows to do GraphQL requests with single line instead of boiler plate utils in every project
• - Provide GraphQL process function for paginated results and fetch all if one needs to load all paginated results into memory.

[wizzy25]

Thanks for creating this. This is actually a great idea to get the new SDK to be stable. And I think these - especially with the sync actions - should be taken as a priority

cc @daern91