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

Fix idom.run and more renaming of server to backend #763

Merged
merged 3 commits into from
Jun 17, 2022
Merged

Conversation

rmorshea
Copy link
Collaborator

@rmorshea rmorshea commented Jun 16, 2022

Description

Renames idom.server to idom.backend also renamed ServerFixture to BackendFixture + DisplayFixture.server to DisplayFixture.backend.

Checklist:

Please update this checklist as you complete each item:

  • Tests have been included for all bug fixes or new functionality.
  • The changelog.rst has been updated with any significant changes.
  • GitHub Issues which may be closed by this Pull Request have been linked.

@rmorshea rmorshea merged commit d157e10 into main Jun 17, 2022
@rmorshea rmorshea deleted the fix-idom-run branch June 17, 2022 00:56
@Archmonger
Copy link
Contributor

Archmonger commented Jun 17, 2022

@rmorshea Should we add a task to v2 to have functional tests for idom.run?

@rmorshea
Copy link
Collaborator Author

It actually looks like there is a test. Not sure why it didn't catch it.

@Archmonger
Copy link
Contributor

I wasn't able to locate the test in the repo. But perhaps it's not checking running via the default (unspecified) server implementation?

@rmorshea
Copy link
Collaborator Author

rmorshea commented Jun 17, 2022

Ah, yup. That's exactly it.

@rmorshea
Copy link
Collaborator Author

The trouble is that we have to specify the implementation as Flask because the others don't play nice in threads.

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.

None yet

2 participants