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

feat(migration_name): allow migrations with custom table name #124

Merged
merged 3 commits into from
Apr 4, 2021

Conversation

aleDsz
Copy link
Contributor

@aleDsz aleDsz commented Mar 30, 2021

As requested from issue, this PR allows to use migration with custom schema names from the config. I also added the temporary_env dependency that allows to test temporary configs from the application.

Feel free to make changes :)

Closes #118.

@aleDsz aleDsz requested a review from a team as a code owner March 30, 2021 01:41
schema_name =
:guardian
|> Application.fetch_env!(Guardian.DB)
|> Keyword.get(:schema_name, "guardian_tokens")
Copy link
Member

Choose a reason for hiding this comment

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

I would suggest to add some documentation about it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmmm, where's the best location for it? README or moduledoc?

Copy link
Member

Choose a reason for hiding this comment

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

For the most part, moduledoc first and then README

@yordis yordis merged commit fcfc3fb into ueberauth:master Apr 4, 2021
@yordis
Copy link
Member

yordis commented Apr 4, 2021

🚀 🚀 🚀 🚀 🚀

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.

Documentation: need to update migrations if using non-default table name
2 participants