hypothesis
Generic usage of LMS API
This PR doesn't add a groundbreaking change to the codebase but I reckon it paves the way to better isolate LMS differences without having to invent new mehcaiims (eg. our plugins), just move LMS specific behavior to the LMS specific service.
Can you update the PR title and description to summarize the changes and context. I can infer what is going on from the code and some recent Slack discussions, but I think it would be helpful for the record.
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
Closing this for now. I reckon there's a good idea here, I'll come back to it when I have some downtime.