2.x.x release notes
2.1.1.RELEASE
-
bugfix:
Style
class is nowSerializable
-
a
HiddenFormElement
can now be converted into aFormControlElement
, see the specific documentation for use cases -
addition of
ScriptViewElement
for writing<script>
tags-
with transparent support for nesting elements in order to generate HTML templates using
ViewElements
-
2.1.0.RELEASE
-
fixed issues with control name prefixing and added the
ControlNamePrefixAdjuster
implementation-
some utility method
BootstrapElementUtils.prefixControlNames(String)
have been added to cover simple (common) cases -
a guide on control name prefixing has been added to show the right way to change control names
-
2.0.1.RELEASE
-
DateTimeFormElements now have support for
LocalDate
,LocalTime
,LocalDateTime
-
FormViewElement
andFormViewElementBuilder
now allow you to configure either a command object or anErrors
instance directly-
this makes it easier to resolve field errors for the
FormGroupElement
members of the form, without having to know the model attribute name -
when using the
errors
property directly, it is no longer required that the command object binding result is present on the model
-
-
the default builders now usually support localized text patterns for any text property
-
for example:
BootstrapUiBuilders.button().title("#{my.button=Default text}")
-
-
TextboxFormElement
rendered inside aFormGroupElement
which detects field errors, will now render the original input value if there are errors present -
direct use of
BootstrapUiFactory
orBootstrapUiComponentFactory
is now discouraged, these interfaces have been deprecated-
use the stateless
BootstrapUiBuilders
facade instead
-
-
added a
TooltipViewElement
with corresponding builder to quickly generate a tooltip with a default question mark icon-
see
BootstrapUiBuilders.tooltip()
for a builder method
-
-
FormGroupElement
has been refactored to support more descriptions-
a
tooltip
can be set which will be added to the label - after the label text and required indicator -
a
descriptionBlock
can be set which will be added to the group before the control -
a
helpBlock
can be set which will be added to the group after the control -
the property
renderHelpBlockBeforeControl
has been removed as thedescriptionBlock
is always rendered before the control, and thehelpBlock
always after the control
-