You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very good job on the v2.0.0 release. It looks much nicer to work with!
We would like to migrate our repository from the v1.xx to the v2.0.0-testing branch. I have been looking at the sample code, but I have some questions and assumptions that I would like to confirm:
In the readme: What does it mean Most dependencies are use-able without any change., what is the criteria for them to be usable?
Is there a reason the v2.0.0 crypto sample code uses the legacy build mode? Would there be any reason for us to use the legacy build mode?
Is there something hidden that might prevent us from migrating, or that we need to consider?
Thank you very much for your answers!
The text was updated successfully, but these errors were encountered:
Very good job on the v2.0.0 release. It looks much nicer to work with!
We would like to migrate our repository from the v1.xx to the v2.0.0-testing branch. I have been looking at the sample code, but I have some questions and assumptions that I would like to confirm:
Most dependencies are use-able without any change.
, what is the criteria for them to be usable?Thank you very much for your answers!
The text was updated successfully, but these errors were encountered: