Skip to content

Conversation

@moncefarajdal
Copy link

@moncefarajdal moncefarajdal commented Oct 15, 2024

auth_user_case_insensitive Migration to 18.0

Ted Salmon and others added 26 commits October 15, 2024 16:10
…f `_login`

* Update code and tests to override `_login` method
Currently translated at 100.0% (2 of 2 strings)

Translation: server-auth-12.0/server-auth-12.0-auth_user_case_insensitive
Translate-URL: https://translation.odoo-community.org/projects/server-auth-12-0/server-auth-12-0-auth_user_case_insensitive/pt_BR/
Currently translated at 100.0% (4 of 4 strings)

Translation: server-auth-16.0/server-auth-16.0-auth_user_case_insensitive
Translate-URL: https://translation.odoo-community.org/projects/server-auth-16-0/server-auth-16-0-auth_user_case_insensitive/es/
Currently translated at 100.0% (4 of 4 strings)

Translation: server-auth-16.0/server-auth-16.0-auth_user_case_insensitive
Translate-URL: https://translation.odoo-community.org/projects/server-auth-16-0/server-auth-16-0-auth_user_case_insensitive/it/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: server-auth-17.0/server-auth-17.0-auth_user_case_insensitive
Translate-URL: https://translation.odoo-community.org/projects/server-auth-17-0/server-auth-17-0-auth_user_case_insensitive/
@moncefarajdal
Copy link
Author

@dreispt I have migrated the module and tested it locally and it works fine. I'm facing a problem with the test cases. Normally the super()._login method takes login and password but in Odoo 18 it takes a credentials object. I tried modifying the test case to match the new behavior but I can't figure it out.

@moncefarajdal moncefarajdal mentioned this pull request Oct 16, 2024
22 tasks
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 23, 2025
Copy link
Member

@amh-mw amh-mw left a comment

Choose a reason for hiding this comment

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

  1. All the [MIG] commits should be squashed together with the change to the contributors file
  2. The [IMP] pre-commit commit is done before any migration changes; see https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#technical-method-to-migrate-a-module-from-170-to-180-branch

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Mar 2, 2025
Copy link

@JessBrandl JessBrandl left a comment

Choose a reason for hiding this comment

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

Agreed with the other review + small improvement in comment

Comment on lines +23 to +26
raise ValidationError(
_("Conflicting user logins exist for `%s`", login)
)

Choose a reason for hiding this comment

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

Possible small performance improvement according to the migration docs

You can replace the call to translate a string ( _ ) with self.env._ for getting some performance improvement in some cases. See odoo/odoo#174844.

@CRogos
Copy link
Contributor

CRogos commented Mar 28, 2025

  1. All the [MIG] commits should be squashed together with the change to the contributors file
  2. The [IMP] pre-commit commit is done before any migration changes; see https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#technical-method-to-migrate-a-module-from-170-to-180-branch
  1. Also squash commits by weblate, OCA-git-bot and oca-ci

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 27, 2025
@github-actions github-actions bot closed this Aug 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.