Skip to content
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

flask demo: don't provide a meaningless default server #163

Merged
merged 1 commit into from
Jul 19, 2024
Merged

Conversation

mikix
Copy link
Contributor

@mikix mikix commented Jul 19, 2024

Instead, ask the user to provide the test server. Which is annoying, but...

The flask demo needs an OAuth-capable server, and we are currently using a no-auth server, so the user just sees a message "nothing to demo here".

This is because:

  • The old (oauth) server that presumably worked was taken down.
  • We put in the new (non-oauth) R4 modern test server.
  • The modern server has a temporary bug where its metadata doesn't validate
  • So we didn't notice that the flask server wouldn't work even if validation passed.

All of the public test servers I know about require you to email someone to set up a user. So it's not obvious what a good replacement would be.

Honestly, we should probably just add a new default demo that supports no-auth servers and still shows something interesting.

But for now, this gets the flask demo to a more honest place and asks the user to provide their own server. 🤷

Fixes #162
Fixes #86

Instead, ask the user to provide the test server. Which is annoying,
but...

The flask demo needs an OAuth-capable server, and we are currently
using a no-auth server, so the user just sees a message "nothing to
demo here".

This is because:
- The old server that presumably worked was taken down.
- We put in the new R4 modern test server.
- The modern server has a temporary bug where its metadata doesn't
  validate
- So we didn't notice that the flask server wouldn't work even if
  validation passed.

All of the public test servers I know about require you to email
someone to set up a user. So it's not obvious what a good replacement
would be.

Honestly, we should probably just add a new default demo that supports
no-auth servers and still shows something interesting.

But for now, this gets the flask demo to a more honest place and asks
the user to provide their own server. 🤷
Copy link
Contributor

@dogversioning dogversioning left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i guess this gives us a chance to try an open source FHIR server out for a new testbed.

@mikix mikix merged commit efcaade into main Jul 19, 2024
5 checks passed
@mikix mikix deleted the mikix/flask-fix branch July 19, 2024 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Handle R4 reference server not returning valid FHIR Flask app still failing on non-optional property 'type'
2 participants