SDK Update Best Practices

Announcements

Live Webinar: USB-C adoption. Simple & Cost-efficient solutions | April 18th @9am or 5pm CEST. Register now !

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
KevinR_91
Employee
Employee
25 replies posted 10 likes received 10 replies posted

Is there a best practices guideline for how I should add custom code while using the SDK to ensure that nothing, or as little as possible breaks when I do an update to a new SDK?

Aside from release notes does Cypress provide any other guidance on how best to update to a new SDK to limit the impact to custom code?

0 Likes
1 Solution
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Recommend you add additional head file and .c file for all of customize function and defines. And add into the SDK example project and use Marco define. When you have to upgrade to next version, You can just make those changes and search with MARCO define. And the version management tool is recommended.

Best Regards,

Lisa

View solution in original post

0 Likes
1 Reply
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Recommend you add additional head file and .c file for all of customize function and defines. And add into the SDK example project and use Marco define. When you have to upgrade to next version, You can just make those changes and search with MARCO define. And the version management tool is recommended.

Best Regards,

Lisa

0 Likes