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][IMP] mis_builder: take field context into account #591

Open
wants to merge 3 commits into
base: 16.0
Choose a base branch
from

Conversation

IT-Ideas
Copy link

@IT-Ideas IT-Ideas commented Dec 22, 2023

[IMP] mis_builder: take field context into account
Prior to this commit only the action context was taken into account
when looking for the mis_analytic_domain key in the context.

This commit adds the support of the field context, where self
can be used in order to inject record data in the context.

Blocked by #585

@OCA-git-bot
Copy link
Contributor

Hi @sbidoul,
some modules you are maintaining are being modified, check this out!

@IT-Ideas
Copy link
Author

Blocked by #585

This commit ensure that the context used by the `mis_report_widget`
widget RPC calls is correctly computed.

Previously using the `mis_analytic_domain` context key was useless
as not taken into account in the widget.
@IT-Ideas IT-Ideas force-pushed the 16.0-mis-builder-allow-passing-analytic-account-field branch from c506690 to b4fcca2 Compare December 27, 2023 13:58
@IT-Ideas IT-Ideas changed the title 16.0 mis builder allow passing analytic account field [IMP] mis_builder: allow passing analytic account field name Dec 27, 2023
@IT-Ideas
Copy link
Author

Rebased

…ll-down

Prior to this commit the state of the searchModel was lost when navigating
back from a drill-down.

This commit uses the globalState in order to store and restore the state
of the searchModlel. The use of a SubEnv allows not having to pass props
up to the widget, which would have required overriding the renderer, the
compiler and field.
@IT-Ideas IT-Ideas force-pushed the 16.0-mis-builder-allow-passing-analytic-account-field branch from b4fcca2 to 62e6e29 Compare January 16, 2024 18:19
@IT-Ideas IT-Ideas changed the title [IMP] mis_builder: allow passing analytic account field name [IMP] mis_builder: take field context into account Jan 16, 2024
Prior to this commit only the action context was taken into account
when looking for the `mis_analytic_domain` key in the context.

This commit adds the support of the field context, where `self`
can be used in order to inject record data in the context.
@IT-Ideas IT-Ideas force-pushed the 16.0-mis-builder-allow-passing-analytic-account-field branch from 62e6e29 to ed9eec9 Compare January 17, 2024 07:45
@sbidoul sbidoul changed the title [IMP] mis_builder: take field context into account [16.0][IMP] mis_builder: take field context into account May 10, 2024
@sbidoul sbidoul added the 16.0 label May 10, 2024
Copy link

github-actions bot commented Sep 8, 2024

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 Sep 8, 2024
@github-actions github-actions bot closed this Oct 13, 2024
@sbidoul sbidoul reopened this Oct 13, 2024
@OCA-git-bot
Copy link
Contributor

Hi @sbidoul,
some modules you are maintaining are being modified, check this out!

@sbidoul sbidoul removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Oct 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants