Update mod-users to custom-fields 1.4.0

@Dima Tkachenko Thank you.

How might those changes be described in release notes?

support for a new fields type: Repeatable Field

Custom fields can have multiple values?

update to Multi-select/Single-select/Radio field (MODCFIELDS-43): the way options for this type of fields are handled has been changed (it's a breaking change)

Selectable options for custom fields must have a unique identifier?

Recent mod-custom-fields release includes two major changes:

• support for a new fields type: Repeatable Field (MODCFIELDS-37)

• update to Multi-select/Single-select/Radio field (MODCFIELDS-43): the way options for this type of fields are handled has been changed (it's a breaking change)

because of the above, the interface version was updated to 2.0

@Dima Tkachenko @Pavlo Smahin

As part of the upgrade of the custom-fields library dependency, the interface provided changed to 2.0. I was a little surprised that a minor library upgrade caused a breaking compatibility change.

I'm trying to prepare the release news for mod-users, please could you help me understand what has changed?

@Dima Tkachenko

mod-users-bl doesn't have a dependency to custom-fields (it least I don't see any in pom.xml)

Sorry, I meant mod-users

Don't know about the rules in the Core Functional team but in Spitfire we usually update the dependencies ourselves before the release, the same way as we update the dependency to a new version of RMB. Custom fields in mod-users is rather an exception because the Spitfire team developed the feature and we take care of it

Agreed, Core Functional updated RAML Module Builder in the modules it is responsible for. For other library dependencies, I tend to consider that the responsibility of the team needing / making the changes.

Does this mean that you expect the Core Functional team to update the dependency in mod-users-bl to 1.4.0?

Hey, @Marc Johnson
mod-users-bl doesn't have a dependency to custom-fields (it least I don't see any in pom.xml)

Don't know about the rules in the Core Functional team but in Spitfire we usually update the dependencies ourselves before the release, the same way as we update the dependency to a new version of RMB. Custom fields in mod-users is rather an exception because the Spitfire team developed the feature and we take care of it