[
https://issues.apache.org/jira/browse/RAVE-1047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750426#comment-13750426
]
Erin Noe-Payne commented on RAVE-1047:
--------------------------------------
Ok, I was actually making this ticket with the intention of being more in line
with what you have been emphasizing. My thought was that since a regionWidget
only has meaning in the context of a page and region, then it should have a
reference to those things so that it makes sense on its own.
We are not always retrieving regionwidgets from their canonical url, so I don't
necessarily have the pageId / regionId info from the path. Specifically the
pagesForRender endpoint gives me back pages, regions, regionWidgets. So given
that data model I would need to recreate references on the client between the
page, region and regionWidget if I need that information.
> 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
