You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
We had a little discussion on the RO.NET forum[1] about contributed actions and we agreed that a sub-menu hint would be all that is needed to support this special grouping.
I'd prefer "grouping" or "group" to "subMenu" - because then it could be applied to properties. N.B. It was long the intention that Naked Objects (for Java) would support grouped properties but never implemented, I think. In NO.NET the need was partially obviated by Complex Types, though grouping of properties might still be useful.
Can I suggest that the format of the grouping anticipated sub-grouping, perhaps by being a comma separated list?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We had a little discussion on the RO.NET forum[1] about contributed actions and we agreed that a sub-menu hint would be all that is needed to support this special grouping.
{
"memberType": "action",
"subMenu":"Orders"
...
}
Typing that out now I wonder if just the more generic "grouping":"Orders" is appropriate?
This would probably not be a per-instance kind of thing so maybe extensions and the formal domain model is where it belongs.
[1] http://restfulobjects.codeplex.com/discussions/389386
The text was updated successfully, but these errors were encountered: