piano_id 1.0.8
piano_id: ^1.0.8 copied to clipboard
Piano ID Flutter SDK.
1.0.8 #
- The Piano ID requests and
PianoIDSignInWidgetcarry the newPianoClient.userAgentas theirUser-Agent, which names the operating system and the device the way the native Piano SDKs do, rather thanPiano SDK for Flutter v<version> (Flutter; <aid>) - The Piano ID requests are sent with
PianoClient.httpClient, so they reuse the connections of the instance and fail oncePiano.closehas closed it; a request that fails throws theClientExceptionofpackage:httprather than theSocketExceptionorHttpExceptionofdart:io, though the one for a socket failure still implementsSocketException - General improvements
1.0.7 #
- General improvements
1.0.6 #
- General improvements
1.0.5 #
- Added social sign-in through OAuth providers: implement
PianoIDOAuthProviderand list it in thePianoIDConfiguration(providers: [...])passed toPiano.init. The configuration is optional —piano.id()works without one, offering Piano ID's own login alone - Piano ID no longer keeps its state for the whole process: the deployment host
moved to the
PianoIDModuleof the instance, so instances carrying different AIDs no longer share what one of them looked up.piano.id()still returns a new client every call, and the clients of an instance share its module - The deployment host is looked up once per instance even when the first requests are made at the same time: the requests that come while the lookup is on its way wait for it rather than each starting one of their own
- The consents a request reports are encoded for that request rather than once
per process: a reader who changes what they consented to through
PianoConsents.setis no longer reported to Piano ID with the decision they have taken back - Requires Dart 3.13.2 and Flutter 3.47.2 or newer
1.0.4 #
- General improvements
1.0.3 #
- The sign-in screen is now localized with the
languagecode fromPiano.init
1.0.2 #
- General improvements
1.0.1 #
- General improvements
1.0.0 #
- Initial release of piano_id package