Skip to content

Releases: json-schema-form/angular-schema-form

0.8.14

06 Aug 14:23
Compare
Choose a tag to compare
0.8.14 Pre-release
Pre-release

Note: some regressions have been reported on this release, a bug fix is in the works, you may wish to downgrade back to 0.8.13 in the meantime. Please report any issues you find and provide your schema and form in a plunker so we can add more test cases to ensure greater stability in the update.

This release is to remove features deprecated in AngularJS and release previously added enhancements that should be stable enough for release while awaiting the next 1.0.0 release from the development branch.

Changes

Fixed

  • #578 Ensure key is set in fieldsets
  • #672 Problems with model binding when using nested Arrays
  • #705 sfNewArray: Adding test for new titleMapValues binding.
  • #723 Update links with json-schema-form team addresses
  • #725 Use the firstElementChild property to support templates with whitespaces
  • #726 Fix spec: should generate default form def from a schema
  • #771 Obey pristine success option
  • #906 port condition loop from development branch for IE fix
  • #978 Remove angular.uppercase for AngularJS 1.7 compatibility

Thanks to the following for help with updates or testing related to the changes bundled in this version:
@chargrove @Deklin @edclements @elbunuelo @joelwkent @jozefizso @kyse @LeonardoGentile @nicklasb @rthaut @zackbloom

1.0.0-alpha.4

17 Apr 11:28
Compare
Choose a tag to compare
1.0.0-alpha.4 Pre-release
Pre-release

This is the fourth (of many) alpha and is NOT ready for production yet.

This alpha fixes a bunch of array and destroyStrategy bugs.

Known issues

  • In Angular 1.5+ some odd behaviours can occur if refreshing a form with a flash of content experienced
    The digest cycle is getting stuck under some unknown conditions which is most likely related

Changes

Fixed

  • #602 Custom validator's message not showing
  • #689 DestroyStrategy does not trigger when field no longer meets condition
  • #750 Removing an invalid array item doesn't work properly
  • #769 Model inside Array is not cleaned when Condition fails
  • #857 Regression boolean values only saving true to model
  • Fixes angular-schema-form-bootstrap#41 Place holder does not disappear even after a valid field is selected. Thanks to @ramakrij

1.0.0-alpha.3

02 Apr 10:16
Compare
Choose a tag to compare
1.0.0-alpha.3 Pre-release
Pre-release

This is the third (of many) alpha and is NOT ready for production yet.

ADD-ONS should now be WORKING again

This alpha also fixes a few bugs like the annoying Invalid type, expected array error when an array content is invalid.

Changes

Fixed

  • Arrays update validity more consistently, removed Angular version specific code
  • Add-ons will now correctly display by the added type being passed to the core correctly
  • #750 Unstoppable "Invalid type, expected array" when form initialised with incorrect array content.
  • #633 #602 custom validator errors.
  • #558 Add check for schema property to prevent form generation failures when a checkbox is explicitly defined by a developer (and therefore does not have a schema property) by @vinceis1337 in #663

1.0.0-alpha.2

19 Feb 13:43
Compare
Choose a tag to compare
1.0.0-alpha.2 Pre-release
Pre-release

This is the second (of many) alpha and is NOT ready for production yet.

There is only one change in this alpha that needs user testing and feedback, the long awaited and much desired support for $ref.

Changes

Added

1.0.0-alpha.1

04 Feb 12:40
Compare
Choose a tag to compare
1.0.0-alpha.1 Pre-release
Pre-release

This is an early preview of the separated json-schema-form-core version of angular-schema-form
Thanks to @davidlgj for starting the separation, tests and the initial Webpack build
Completed by @Anthropic with the additional tests and upgraded Webpack 2 build process

This is the first (of many) alpha and is NOT ready for production yet.

Changes

Breaking

  • Some add-ons will not be working yet, if an add-on is updated to use the new function it should work again, but there is more work to do here to make the upgrade seamless before a beta can be released.
  • Decorators should be updated to use the defineDecorator syntax with builders prior to the 1.0.0 release.

Added

  • 23 test cases added to ASF and a further 30 test cases to json-schema-form-core
  • Integration with json-schema-form-core, this is the main purpose of this release as we move as much code to plain Javascript es6+ as possible to re-use the code in an Angular 2+ release
  • #596 arrayIndices allows access to the current path for conditions in pr #742
  • #560 All fields should now have classes, names and ids that match and can be used for easier test writing and scripting. The classes are provided with and without array indexes so they can be accessed as a group or individually, fixed in PR #578
  • #748 New key, include all undefined schema fields in the form that are not already added with [ '...' ]

Fixes

  • Tests fixed and running
  • Travis builds fixed and running
  • #828 schemaFormValidate event doesn't trigger past v0.8.2
  • #680 Pristine option was not behaving in pr #771
  • Add support for templates with leading whitespaces in pr #725
  • Improve sfNewArray Directive's titleMapValues Binding in pr #705
  • #590 Problems with model binding when using nested Arrays in pr #672, #742
  • Pass optional form name when broadcast error in in PR #656
  • Fix for #121 to redraw with proper defaults in PR #647
  • Revalidate model after successful custom validation event broadcasted in PR #642
  • Fixed angular element children selector usage partially in PR #605
  • Allow broadcasting of the formName to validate in PR #589
  • Ensure key is set in fieldsets in PR #578

TODO

The remaining work for v1.0.0 will revolve around:

  • $ref for local based on workaround example provided by @AndreNel7
  • *Of
  • fix regressions from prior to 0.8.13
  • fix high priority issues from prior to 0.8.13
  • design and integrate a new API to work with json-schema-form-core
  • Providing a method to run legacy add-ons not using the builders
  • Create npm organisation prefix @json-schema/angular

The addition of highly requested items like $ref will become available in subsequent alpha releases. The rest will be looking for community PRs and support.

Special thanks to all the following people for their help in the last year preparing for the move to this version:
@AndreNel7 @apinnecke @blackmiaool @CatherineH @cepauskas @chargrove @donalmurtagh @edclements @elbunuelo @ErichBSchulz @jozefizso @illiano @kyse @LeonardoGentile @mathroc @plong0 @pvgnd @stanimoto @tisto @tomsowerby @zackbloom

Extra special thanks to @handrews @joelwkent @nicklasb for insight, ideas and support as we head toward version 1.0.0!

Also like to thank all the people who have created great issues with plunkers and suggestions, you really make a difference.

...really really hope I haven't missed anyone (let me know if you feel I have!)

0.8.13

04 Apr 08:19
Compare
Choose a tag to compare
  • Bugfix copy the initial form default on form redraw @stanimoto
  • Bugfix for revalidating the model after custom validation event is broadcast @cepauskas
  • New event value. The form name is now passed in validate and error events @tomsowerby & @LeonardoGentile
  • Add missing comma to examples @tisto

0.8.12

30 Sep 08:39
Compare
Choose a tag to compare
  • Bugfix for condition builder. It had a typo that broke it.
  • Bugfix for transclusion builder.

0.8.11

25 Sep 21:01
Compare
Choose a tag to compare
  • Bugfix for checkbox validation in the new builder.

0.8.10

24 Sep 20:48
Compare
Choose a tag to compare

Bugfix for tyep checkboxes. It threw an error when model array was undefined.

v0.8.9

18 Sep 09:17
Compare
Choose a tag to compare
  • Bugfix for radios and radios-inline. Validation should now work.
  • Bugfix so model changes from outside the form trigger validation.
  • New global option pristine. Sets if errors and success states
    should be visible when form field are $pristine. Default is {errors: true, success: true}.