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

[14.0] [mig] pos_fix_search_limit #665

Closed
wants to merge 21 commits into from

Conversation

fshah-initos
Copy link
Contributor

No description provided.

@hkapatel-initos
Copy link
Contributor

It would be nice if we could get reviews here.

Copy link
Contributor

@hkapatel-initos hkapatel-initos left a comment

Choose a reason for hiding this comment

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

code review:LGTM

@hkapatel-initos
Copy link
Contributor

Hello, @ivantodorovich can you please check it again so we should merge it ASPS.

@ivantodorovich
Copy link
Contributor

Hello, @ivantodorovich can you please check it again so we should merge it ASPS.

Hi, the implementation changed a lot and it was significatly simplified.
I don't use this module so I don't have enough knowledge to review. I rather the original module's authors
/ contributors review this.

@hkapatel-initos
Copy link
Contributor

Hello, @hparfr and @dalonsod it would be great if you both can add reviews here.

@hparfr
Copy link
Contributor

hparfr commented Sep 17, 2021

Pos_fix_search_limit can't be migrated without lot of code changes. The new layout of functions don't allow enough modularity. So I integrated this feature in the pos_product_template here:

akretion@d872722#diff-3e277683278bdd486fadd6746e8669da4432e49edddbd6f24b66343f83b0b51eR91

Do you need pos_fix_search_limit in another context ?

@dsolanki-initos
Copy link
Contributor

Hello, @hparfr and @ivantodorovich it would be nice if you re-check.

@dsolanki-initos

This comment was marked as duplicate.

1 similar comment
@dsolanki-initos

This comment was marked as duplicate.

@dsolanki-initos

This comment was marked as duplicate.

@legalsylvain legalsylvain added this to the 14.0 milestone Mar 6, 2022
@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 10, 2022
@ikapasi-initos

This comment was marked as duplicate.

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jul 17, 2022
@ikapasi-initos

This comment was marked as duplicate.

@OCA OCA deleted a comment from ikapasi-initos Sep 23, 2022
@legalsylvain
Copy link
Contributor

Closing, as question from @hpar is unanswered since 1 year.

Feel free to reopen after having answered.
Thanks.

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.

None yet