Added string[] as valid type for scope in config

[matthewstrom]

The actual JavaScript for OktaAuthModule accepts a string array for the scope property of the config; however, the faulty type definition causes compilation to fail when scope is an array.

[robertjd]

Thanks for this PR! We’re actually trying to move to a world where scope is always defined as a string (per OAuth norms) so we want to leave this as a string. Ideally, we should only be checking for the only String type here. If you’d like to update this PR to remove that snippet instead, we will get this merged in ASAP!

[matthewstrom]

Is that to say that a space-delimited list of scopes will work?

By "remove that snippet", are you proposing that line 162–165 in okta.service.ts should be removed? Won't that break backward compatibility?

Perhaps some better documentation is in order? Something that indicates that scope accepts a space-delimited list.

[matthewstrom]

Is that to say that a space-delimited list of scopes will work?

By "remove that snippet", are you proposing that line 162–165 in okta.service.ts should be removed? Won't that break backward compatibility?

Perhaps some better documentation is in order? Something that indicates that scope accepts a space-delimited list.

[cmckni3]

I modified the parameter of scrubScopes in #116. Do you want me to remove the string[] type and the related code @robertjd?

[robertjd]

Thanks all for pointing this out, in 1.0 we're going to make this string-only. See #120

[jmelberg-okta]

This fix has been included with the 1.0.0 release of @okta/okta-angular See #157 and #167 for more details!