[
https://issues.apache.org/jira/browse/RAVE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750454#comment-13750454
]
Erin Noe-Payne commented on RAVE-1047:
--------------------------------------
Ok, I think I missed that discussion.
This could be a solution. My only concern here is that the data we get back
from pagesForRender needs to be decomposed into individual resources such that
further interaction (add, delete, edit, move, hide / show of pages,
regionWidgets) happens through the crud endpoints. So the farther we separate
the pagesForRender models from the rest models, the greater the risk of
impedance.
> RegionWidget model should have a pageId field
> ---------------------------------------------
>
> Key: RAVE-1047
> URL: https://issues.apache.org/jira/browse/RAVE-1047
> Project: Rave
> Issue Type: Improvement
> Reporter: Erin Noe-Payne
> Fix For: 0.23
>
>
> A regionWidget is uniquely defined by its page, region and widget id's. The
> regionWidget model should have a reference to make operations involving
> moving or deleting on the client.
--
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
