[
https://issues.jboss.org/browse/FORGEPLUGINS-126?page=com.atlassian.jira....
]
Vineet Reynolds resolved FORGEPLUGINS-126.
------------------------------------------
Resolution: Done
Pushed upstream into a separate branch:
https://github.com/forge/angularjs-scaffoldx-plugin/tree/FORGEPLUGINS-126
This will need to be merged into the master branch after Forge 1.4.0 containing FORGE-1060
is released.
Rework the AngularJS scaffolding to support the new REST resource
representations
---------------------------------------------------------------------------------
Key: FORGEPLUGINS-126
URL:
https://issues.jboss.org/browse/FORGEPLUGINS-126
Project: Forge Plugins
Issue Type: Feature Request
Components: AngularJS Scaffold
Reporter: Vineet Reynolds
Assignee: Vineet Reynolds
Priority: Critical
Based on the ongoing work for FORGE-1060, it would be necessary to rework the logic for
handling associations (both n-to-many and n-to-one) since only Ids of the associated
fields are required now.
Additional fields that are not a part of the associated resource's representation
should not be sent to the server, since it is possible that the server may treat such
fields in the incoming JSON representation as not ignorable and respond with a HTTP 400
error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira