Closed mraible closed 7 years ago
@mraible It looks like the JSDK is returning a list of groups, rather than a collection map (which has an items property, which is a list). I'm not seeing this explicitly defined in our framework spec, but in practice I'm pretty sure everyone is doing the later. Ping @bretterer and @nbarbettini
Yes @robertjd, the .NET middleware returns a faux-collection that includes size
and items
property. Specifically so it will work with this Angular code. :)
@dogeared and @lhazlewood It looks like we need to change the Java SDK to return groups.items
instead of just groups
.
Created an issue for this in the Java SDK: https://github.com/stormpath/stormpath-sdk-java/issues/1044
Re-opening because the fix on the Java SDK will break semver. We'll be able to release a fix in 2.0, but in the meantime, I'll create a PR to workaround this issue in the AngularJS SDK.
Closing because fixed in Java SDK: https://github.com/stormpath/stormpath-sdk-java/issues/1044
In the Java SDK, /me (with groups expansion) returns groups data as follows:
When I use
if-user-in-group="ADMIN"
, I see the following error in my console:If I look at line 2895 in
stormpath-sdk-angularjs.js
, I see the following function being called:The logic still seems to work, and I am using the if-user-in-group directive, but there seems to be a bug here. If I debug,
this.groups
is defined, butthis.groups.items
is not.