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
Currently, FCL data models (e.g. services, responses, & other nested objects) are versioned (generally v1.0.0). However, the library does not perform and form of semantically versioned matching when "normalizing" these services.
The result is that FCL is unable to comprehend a version which, by the rules of semver, should be valid. (e.g. if FCL encounters a v1.1.0 authentication service, it cannot proceed, despite the fact that it should be compatible with all v1.x.x authentication services).
This is a part of a larger protocol issue related to versioning onflow/flips#238, however, it can likely be patched in FCL-JS independent from an FCL protocol bump. However, this wallets should not assume that FCL clients will honour semantic versioned data structures after the patch (as this assumption would break older FCL clients).
Suggest A Solution
No response
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered:
Issue to be solved
Currently, FCL data models (e.g. services, responses, & other nested objects) are versioned (generally
v1.0.0
). However, the library does not perform and form of semantically versioned matching when "normalizing" these services.The result is that FCL is unable to comprehend a version which, by the rules of semver, should be valid. (e.g. if FCL encounters a
v1.1.0
authentication service, it cannot proceed, despite the fact that it should be compatible with allv1.x.x
authentication services).This is a part of a larger protocol issue related to versioning onflow/flips#238, however, it can likely be patched in FCL-JS independent from an FCL protocol bump. However, this wallets should not assume that FCL clients will honour semantic versioned data structures after the patch (as this assumption would break older FCL clients).
Suggest A Solution
No response
What are you currently working on that this is blocking?
No response
The text was updated successfully, but these errors were encountered: