-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API Verifier standalone mode does not work correctly #220
Comments
Something's amiss with http://apiverifier.smartplatforms.org/smartapp/index.html as well... need to trace |
I'm checking this out locally, but did sandbox.smartplatforms.org with the latest code go away? |
Not sure what you mean... sandbox should be in place as usual |
We have no hosted server with pre-1.0 code then? That's ok. Just checking. |
Also, what was the correct behavior of the verifier in standalone mode? There was no record_id, correct? |
Well... the current public sandbox is 0.6 (which is pre-1.0 technically). What I mean by "standalone mode" is that the API Verifier could be launched outside of a container and it would detect that state through the SMART connect client and respond by degrading. Try out the API Verifier from SMART 0.5 on its own (not through SMART) for comparison: |
... or try the 0.5.3 VM: http://docs-v06.smartplatforms.org/downloads/vm/ |
Correct behavior (in the old verifier):
http://apiverifier-v05.smartplatforms.org/smartapp/index.html
Incorrect behavior (in the current verifier):
http://apiverifier-v06.smartplatforms.org/smartapp/index.html
The text was updated successfully, but these errors were encountered: