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 Nov 9, 2017. It is now read-only.
The current algorithm merges ASAP (to avoid building a tree).
Which supposedly work, but sadly RoutableResources, RoutableMember and RoutableCollection are instances of AbstractRoutable.
Which means that the three of them got the "$name" property. We should be using a PRIVATE property on RoutableResource(s) so that the Name Resolving doesn't add BOTH the name of the RoutableResource(s) AND the name set when created the Routable{Member,Collection}.
Or so I think ... Maybe I fixed it already (by nulling the name before creating the RoutableResources's sub routes)