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

Use public Synapse imports for UserID and run_as_background_process #175

Merged
merged 2 commits into from
Feb 11, 2022

Conversation

reivilibre
Copy link
Contributor

The general rule is: synapse.module_api is OK, but anywhere else is not.

Luckily the other two things are already exported for public use. We don't guarantee the stability/existence of functions in other parts of the code.

Related: #173, #174.

Copy link
Contributor

@Yoric Yoric left a comment

Choose a reason for hiding this comment

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

Looks good!

@Yoric
Copy link
Contributor

Yoric commented Feb 7, 2022

The test failures seem unrelated. It seems that you based your branch on a version that had... a few CI issues :)

I'm in the process of adding (some) CI for the Synapse module as part of #128, so I suggest:

  1. we wait until Let's port to Synapse module API #128 has landed;
  2. then @reivilibre rebases his code, to get the latest CI;
  3. then we move to land this.

@reivilibre
Copy link
Contributor Author

@Yoric CI is happy now — if you're happy with it, please (squash) merge.

@Yoric Yoric merged commit e49e4d0 into main Feb 11, 2022
@Yoric Yoric deleted the rei/use_public_imports_where_possible branch February 11, 2022 09:13
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.

2 participants