s99 | 99 Scala problems as a set of specs2 specifications

Currently, you are not appending anything to listing_details. Your for loop should look something like this:

Would you please try the following:

There's no solution which avoids calling sin and cos, aside from precomputing them for all useful values of N. However, you only need to do the computation once, regardless of N. (Provided you know where the centre of the polygon is. You might need a second computation to figure out the coordinates of the centre.) Every vertex can be computed from the previous vertex using the same rotation matrix.

The lookup table of precomputed values is not an unreasonable solution, since at some sufficiently large value of N the polygon becomes indistinguishable from a circle. So you probably only need a lookup table of a few hundred values.

This is less of a angular/ag-grid question as it is a question to design an algorithm for your desired sort behavior. It seems you've figured everything out except the comparator function.

But we need some more details. From your small example it looks like your algorithm can simply cut off the first char of each string, and simply sort by the numbers remaining. But what other kind of strings will you be expecting? Will each string always be 'S' followed by digits? If that's the case then what I just described will work.

But if each string will have x number of characters followed by y number of digits, then you will need to split your strings into two parts (chars & digits). Then sort first by chars and then by digits.

Edit: Op has specified that the string is always an 'S' followed by digits, so I'm writing the custom comparator function here.

You can use explode and enumerate the students, and then groupby:

I just found this thesis, maybe it would help you to keep looking. https://pastel.archives-ouvertes.fr/tel-01762479/document

TL;DR https://en.wikipedia.org/wiki/LCP_array https://en.wikipedia.org/wiki/Suffix_array

python https://louisabraham.github.io/notebooks/suffix_arrays.html

It's not very clear how old the documentation is (by the link you provided) and is it relevant to your case.

I know that different Identity Providers can work slightly different. And I know cases when you should make a separate call with obtained ID token to /userinfo endpoint to get user info.

There is some different Google documentation for Google Identity Platform.

1. It has description of ID tokens.

   https://developers.google.com/identity/protocols/OpenIDConnect#obtainuserinfo

   Google ID Tokens may contain the following fields (known as claims):

   Notice that it doesn't have always in Provided column. I think that it could be different for different APIs.

2. The same docs have section "Obtaining user profile information"

   It explains where to get the /userinfo endpoint URL and how to call it. In the response you should receive the info you need.

My guess why it's not working in your case is that you are using /tokeninfo endpoint. It's not a part of OpenID Connect standard. It just validates the token and parses it (does the same job as https://jwt.io). And the original ID token doesn't contain that claims for some reason. Therefore /tokeninfo endpoint doesn't return them to you.

But according to Google's documentation and you should use /userinfo endpoint to obtain user info claims.

You can find description of this endpoint in OpenID Connect specification: https://openid.net/specs/openid-connect-core-1_0.html#UserInfo

5.3 UserInfo endpoint

The UserInfo Endpoint is an OAuth 2.0 Protected Resource that returns Claims about the authenticated End-User. To obtain the requested Claims about the End-User, the Client makes a request to the UserInfo Endpoint using an Access Token obtained through OpenID Connect Authentication.

You could create a key for each entry that is the combination of the product and material group (for example as JSON). Then create a Map with those keys and with arrays as values, initially all empty. Then iterate over the data to populate those arrays. Finally convert that Map to the target structure.

Here's my stab at it (Demo):