[aerogear-dev] Make debugging compatibility issues easier

[Paul Wright]

Hi,

I've been thinking about some simple debugging procedures, seems like 
we'll be asking users to:

1. Reload config json for mobile app (cos something might have changed 
on OpenShift side)

2. Check a Compatibility Matrix <not%20there> to make sure that your 
sdks and services all match up

That second step seems to be a non-optimal user experience, could we add 
compatibility information to config json?

This would mean the user would not have to leave their IDE to check out 
a compatibility issue.

How might it work?

Each update to a service could include the following info:

* compatibleWith

* incompatibleWith

and as part of updating a service, include known compatibility, for 
example with Keycloak Service v2.3.1 you might have

"androidSDKCompatibleWith":[ "2.x.x", "3.x.x" ],

"androidSDKIncompatibleWith":[ "2.0.x" ]

The user can then check the SDK version and take action as required,

WDYT?

Paul

-- 
Paul Wright
Mobile Docs (github: finp)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20180409/ceea0e99/attachment.html