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

[T-6536][15.0][ADD]transfer_client_portfolio, transfer_client_portfolio_commissions: Add new modules #14

Merged
merged 4 commits into from
Sep 25, 2024

Conversation

RogerSans
Copy link

@RogerSans RogerSans commented Sep 4, 2024

This module allows to transfer contacts, activities and opportunities from one user to another.

The pre-commit error are caused by other modules

T-6536

@HaraldPanten
@ValentinVinagre
@luis-ron

@RogerSans RogerSans marked this pull request as draft September 4, 2024 08:54
@RogerSans RogerSans force-pushed the 15.0-T-6536 branch 10 times, most recently from dd68313 to e71aa3c Compare September 5, 2024 15:06
@RogerSans RogerSans marked this pull request as ready for review September 5, 2024 15:07
@Tisho99 Tisho99 force-pushed the 15.0-T-6536 branch 2 times, most recently from 18b9177 to 355ca75 Compare September 17, 2024 11:33
@Tisho99 Tisho99 force-pushed the 15.0-T-6536 branch 3 times, most recently from 4ec405e to c02b33b Compare September 18, 2024 07:32
Copy link

@luis-ron luis-ron left a comment

Choose a reason for hiding this comment

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

Functional Review: LGTM 👍🏻

@Tisho99
Copy link

Tisho99 commented Sep 18, 2024

@manuelregidor Can you review?

@manuelregidor
Copy link

@Tisho99 Pre-commit is failing. Please, let me know when it's fixed and I'll do the technical review. And do you think it is necessary to have three commits?

@Tisho99
Copy link

Tisho99 commented Sep 19, 2024

@manuelregidor None of the pre-commit errors are due to my module, in that case the PR can be approbed, right?

Copy link

@manuelregidor manuelregidor left a comment

Choose a reason for hiding this comment

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

Just two small comments. No need to make changes if you don't think you need to.

Copy link

@manuelregidor manuelregidor left a comment

Choose a reason for hiding this comment

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

LGTM

@ValentinVinagre
Copy link

@Tisho99 Would it take you a long time to fix the bugs indicated in the pre-commit?

Copy link

@ValentinVinagre ValentinVinagre left a comment

Choose a reason for hiding this comment

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

fix pre-commit

@Tisho99
Copy link

Tisho99 commented Sep 23, 2024

@Tisho99 Would it take you a long time to fix the bugs indicated in the pre-commit?

1 hour more or less, there are a lot of errors

@Tisho99
Copy link

Tisho99 commented Sep 23, 2024

Hi @ValentinVinagre @manuelregidor

I have fixed pre-commit.

However, i am not sure if the following fix is correct:

image

Pre-commit told me i have to delete the cr.commit() and refactor the code if it was necessary to do the deletion.

I have only deleted the cr.commit() because the write above should update the database.

What do you think?

@manuelregidor
Copy link

@Tisho99 I don't think the write method writes on the database straightaway, but only after the transactions has finished. If there was an error, all the write operations performed before would be discarded, as the update query would not be triggered.

@Tisho99 Tisho99 marked this pull request as draft September 23, 2024 13:25
@ValentinVinagre
Copy link

Hi @ValentinVinagre @manuelregidor

I have fixed pre-commit.

However, i am not sure if the following fix is correct:

image

Pre-commit told me i have to delete the cr.commit() and refactor the code if it was necessary to do the deletion.

I have only deleted the cr.commit() because the write above should update the database.

What do you think?

cr.commit() was performed because:

  • the changes are needed in the next iteration.
  • you can't wait for the system to do the save, as it takes too long.
    It's necessary to perform a cr.commit(), which will make the pre-commit skip that point.

@Tisho99 Tisho99 marked this pull request as ready for review September 25, 2024 08:47
@Tisho99
Copy link

Tisho99 commented Sep 25, 2024

@ValentinVinagre

I have put again the cr.commit and skipped the pre-commit error.

This can be merged.

You have the activity in T-6536

Copy link

@ValentinVinagre ValentinVinagre left a comment

Choose a reason for hiding this comment

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

LGTM 👍🏻

@ValentinVinagre ValentinVinagre merged commit 47d0e5f into 15.0 Sep 25, 2024
4 checks passed
@ValentinVinagre ValentinVinagre deleted the 15.0-T-6536 branch September 25, 2024 15:11
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.

5 participants