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
The code didn't expect this requirement, as offering and seeking tags are required with a minimum of 1 tag per property by the frontend, for each user (stakeholder). However, GPML admins can remove totally expertise-related tags, so the generic tag assignation machinery for users (stakeholders) need to be adapted to that case.
The text was updated successfully, but these errors were encountered:
[Re #1734]
As explained in the issue, the generic user (stakeholder) tag
assignation machinery was not ready to allow to remove all the tags of
a given relation-category (offering, seeking or expertise), so now we
have refactored the code to allow so. Since, the tags assignation is a
partial thing (per category), the fix is quite more ellaborated, as we
need to keep the old tags that are not part of the target category, so
those are not overriden.
The code didn't expect this requirement, as offering and seeking tags are required with a minimum of 1 tag per property by the frontend, for each user (stakeholder). However, GPML admins can remove totally expertise-related tags, so the generic tag assignation machinery for users (stakeholders) need to be adapted to that case.
The text was updated successfully, but these errors were encountered: