Open MoralCode opened 7 months ago
another option includes simply reclassifying this as a Flutter library. which may or may not be a good choice
For the webhook usecase, tokens probably dont need to be persisted once the hook is set up as the data will simply arrive.
For other usecases we may need to find a way for the consumer of this library to be responsible for persistence
Having a library boundary between the code that persists tokens to secure storage and the code that uses those tokens seems to be a programming/design pattern I haven't seen before. More research may be needed on how best to do this
tbh im sorta leaning towards https://pub.dev/packages/oauth2 since it looks like its made by dart themselves
hmmm that library may not be great... https://github.com/dart-lang/tools/issues/349
will experiment and see how it goes
this library has been found and imported, it just needs to be integrated
turns out https://pub.dev/packages/oauth2_client uses the flutter SDK not strictly dart.
this is breaking CI