You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the res.company model, you have the require_national_number field. On the subscription.request model, there's the display_national_number field, which is computed as EQUAL to the company's require_national_number.
This is really weird to me, because it implies that 'require == display', and 'not require == not display'. See comments in #69
To Reproduce
Affected versions:
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here. (e.g. OS, Python version, ...)
The text was updated successfully, but these errors were encountered:
There hasn't been any activity on this issue in the past 6 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 issue to never become stale, please ask a PSC member to apply the "no stale" label.
huguesdk
added
no stale
Use this label to prevent the automated stale action from closing this PR/Issue.
and removed
stale
PR/Issue without recent activity, it'll be soon closed automatically.
labels
Dec 11, 2023
Module
l10n_be_cooperator_national_number
Describe the bug
On the res.company model, you have the
require_national_number
field. On the subscription.request model, there's thedisplay_national_number
field, which is computed as EQUAL to the company'srequire_national_number
.This is really weird to me, because it implies that 'require == display', and 'not require == not display'. See comments in #69
To Reproduce
Affected versions:
Steps to reproduce the behavior:
1.
2.
3.
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
Add any other context about the problem here. (e.g. OS, Python version, ...)
The text was updated successfully, but these errors were encountered: