Closed andrewatwood closed 3 years ago
I realize now the branch name doesn't match! Realized I had to re-order these changes after starting, whoops.
I've asked @slifty to take a look so I can focus on uploads. Thanks, @slifty!
Reviewing now -- in the mean time it looks like there are some lint errors worth cleaning up!
Lint error cleaned up!
A small bike shed comment around API token in test and the name of the
change
method of the archive source.More importantly though: I'm trying to wrap my head around the references to archives inside of the authentication resource. This might be aided by some class-level documentation that indicates what each resource is responsible for.
Left some comments, as well as added some class-level documentation with the same ideas, let me know if it clears anything up or if you'd still like to see some re-organization.
Looks like this is stalled. @slifty can you take another look?
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Feature
What is the current behavior? (You can also link to an open issue here) No
init
method, the client doesn't require any setup (as it has no real methods ;) ) beyond credentialsWhat is the new behavior (if this is a feature change)? Adds an
init
method that the user must call before proceeding. Theinit
method is required to actually prepare the client to useful things in the session, rather than just validate that the session exists. AuthResource requires ArchiveRepo endpoints to switch to the archive provided in the client config.