If there is a library where all of its content is behind an access_token but the user does not have it, then queries will have no context and the answers will be very generic.
That's kind of a confusing outcome, so we should figure out a distinctive message to show in that case in the webapp.
If there is a library where all of its content is behind an access_token but the user does not have it, then queries will have no context and the answers will be very generic.
That's kind of a confusing outcome, so we should figure out a distinctive message to show in that case in the webapp.
Related to #26