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
With the introduction of JSON endpoints in the CLI, we need a version checking mechanism to error out when a < 0.9.4 version is detected as ddev list and ddev describe is critical for any sort of UI functionality. We've agreed that string parsing is fragile, and as such should not be supported.
What you expected to happen:
Discussion is needed on how to error out. This is a show stopper, text parsing of ddev-list and ddev-describe is to be completely removed. If an incompatible version is detected, how do we want to error out and show the customer? Do we simply show a warning and exit? Do we launch a browser window to ddev download site? etc.
Related source links or issues:
Initial version check discussion brought up in #18
The text was updated successfully, but these errors were encountered:
rfay
changed the title
Error Handling Update: Version Checking
Error Handling Update: Version Checking, ddev availability, ddev error codes
Dec 28, 2017
Feature Request
With the introduction of JSON endpoints in the CLI, we need a version checking mechanism to error out when a < 0.9.4 version is detected as
ddev list
andddev describe
is critical for any sort of UI functionality. We've agreed that string parsing is fragile, and as such should not be supported.What you expected to happen:
Discussion is needed on how to error out. This is a show stopper, text parsing of ddev-list and ddev-describe is to be completely removed. If an incompatible version is detected, how do we want to error out and show the customer? Do we simply show a warning and exit? Do we launch a browser window to ddev download site? etc.
Related source links or issues:
Initial version check discussion brought up in #18
The text was updated successfully, but these errors were encountered: