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

[16.0][MIG] chained_swapper: Migration to 16.0 #691

Closed
wants to merge 26 commits into from

Conversation

kaynnan
Copy link

@kaynnan kaynnan commented Jul 11, 2023

@kaynnan kaynnan marked this pull request as ready for review July 11, 2023 12:53
@kaynnan kaynnan marked this pull request as draft July 11, 2023 12:54
@kaynnan kaynnan force-pushed the 16.0-mig-chained_swapper branch 3 times, most recently from 629cb1e to ae6d806 Compare July 11, 2023 14:08
@kaynnan kaynnan changed the title [16.0][MIG] chained_swapper: Migration to 16.0 [16.0][MIG][WIP] chained_swapper: Migration to 16.0 Jul 11, 2023
@kaynnan kaynnan force-pushed the 16.0-mig-chained_swapper branch 4 times, most recently from ca805f8 to 85a8d6a Compare July 14, 2023 07:56
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 Nov 12, 2023
@pedrobaeza
Copy link
Member

Is this ready to be reviewed?

@kaynnan kaynnan changed the title [16.0][MIG][WIP] chained_swapper: Migration to 16.0 [16.0][MIG] chained_swapper: Migration to 16.0 Nov 12, 2023
@kaynnan kaynnan marked this pull request as ready for review November 12, 2023 16:57
@kaynnan kaynnan marked this pull request as draft November 12, 2023 16:59
@pedrobaeza pedrobaeza removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Nov 12, 2023
@kaynnan
Copy link
Author

kaynnan commented Nov 12, 2023

Is this ready to be reviewed?

Not yet, I was reviewing the code here and I still couldn't resolve the context of when it creates with the SubElement it shows the error "Uncaught Promise > Missing field string information for the field". This occurs when I changed field_view_get to view_get because the previous method is deprecated, but when it is a many2many or many2one field, etree is not generating the element.

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 Mar 17, 2024
@github-actions github-actions bot closed this Apr 21, 2024
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.