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

[12.0][IMP] hr_attendance_rfid: Add record rule #833

Merged
merged 1 commit into from
Oct 20, 2020

Conversation

brian10048
Copy link
Sponsor

@brian10048
Copy link
Sponsor Author

@HviorForgeFlow @JordiBForgeFlow
This should fix the issue when scanning RFID tags and receiving a security error when the RAS user attempts to make an attendance record from the scan

Copy link
Sponsor Member

@marcelsavegnago marcelsavegnago left a comment

Choose a reason for hiding this comment

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

Looks great for me

@HviorForgeFlow
Copy link
Member

@jarroyomorales ready to move forward

@OCA-git-bot
Copy link
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

Copy link
Member

@Saran440 Saran440 left a comment

Choose a reason for hiding this comment

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

Code Reviewed.

@@ -0,0 +1,15 @@
<odoo>
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
<odoo>
<odoo noupdate="1">

Copy link
Member

Choose a reason for hiding this comment

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

If we are adding the noupdate, we should need to add a migration script that will create the rule

Copy link
Member

Choose a reason for hiding this comment

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

Really? even if that ir.model.data record is not already set on the system? OUCH

Copy link
Member

Choose a reason for hiding this comment

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

Or the forcecreate, but I would opt for the migration

Copy link
Member

Choose a reason for hiding this comment

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

Copy link
Member

Choose a reason for hiding this comment

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

I don't know about migration script.
if you add noupdate in code, Will it cause problems?

Choose a reason for hiding this comment

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

Something as hard as this:
https://github.com/OCA/community-data-files/blob/12.0/account_payment_unece/migrations/12.0.1.0.0/post-migration.py#L8 wink

I think this is the best option, better than the force_create

Copy link

@jarroyomorales jarroyomorales left a comment

Choose a reason for hiding this comment

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

Nice! Thank you!

You also need to upgrade manually the manifest version to 12.0.1.0.2 and change the name of the migration folder to the same version (12.0.1.0.2). Then this will be merged with the nobump option

@brian10048
Copy link
Sponsor Author

Nice! Thank you!

You also need to upgrade manually the manifest version to 12.0.2.0.1 and change the name of the migration folder to the same version (12.0.2.0.1). Then this will be merged with the nobump option

I was just getting ready to comment and ask if I should manually update the manifest or if the merge bot was going to be told what to do! Now I have updated and manually bumped the manifest to 12.0.2.0.0 from 12.0.1.0.0

@jarroyomorales
Copy link

@brian10048 Yes, now we have to agree on the version number. It is not a very huge change so maybe instead of 12.0.2.0.0 we could do 12.0.1.1.0. @Saran440 What do you think?

@Saran440
Copy link
Member

I agree with @jarroyomorales
it should be 12.0.1.1.0
and I will merge with nobump

@brian10048
Copy link
Sponsor Author

@Saran440 @jarroyomorales - Version changes made as requested

@etobella
Copy link
Member

@OCA/human-resources-maintainers I think this is ready to merge 😉

@Saran440
Copy link
Member

/ocabot merge nobump

@OCA-git-bot
Copy link
Contributor

What a great day to merge this nice PR. Let's do it!
Prepared branch 12.0-ocabot-merge-pr-833-by-Saran440-bump-nobump, awaiting test results.

@OCA-git-bot OCA-git-bot merged commit 12a75c9 into OCA:12.0 Oct 20, 2020
@OCA-git-bot
Copy link
Contributor

Congratulations, your PR was merged at bab439d. Thanks a lot for contributing to OCA. ❤️

SoporteOperu pushed a commit to SoporteOperu/hr that referenced this pull request Mar 8, 2022
Signed-off-by etobella
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants