We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
follow_wanikani
There is currently some shared logic between sync, and level unlock, which first checks if a user has follow_me enabled, and if they do not, the level unlocker quite literally ignores. This can be seen in process_vocabulary_response_for_user_v2 in WanikaniUserSyncerV2 https://github.com/Kaniwani/kw-backend/blob/master/api/sync/WanikaniUserSyncerV2.py#L132 , called by https://github.com/Kaniwani/kw-backend/blob/master/api/sync/WanikaniUserSyncerV2.py#L286
follow_me
process_vocabulary_response_for_user_v2
The fix is to divorce the logic between sync and manual unlock. This must be a regression for the V2 syncer as this used to work.
The text was updated successfully, but these errors were encountered:
tadgh
No branches or pull requests
There is currently some shared logic between sync, and level unlock, which first checks if a user has
follow_me
enabled, and if they do not, the level unlocker quite literally ignores. This can be seen inprocess_vocabulary_response_for_user_v2
in WanikaniUserSyncerV2 https://github.com/Kaniwani/kw-backend/blob/master/api/sync/WanikaniUserSyncerV2.py#L132 , called by https://github.com/Kaniwani/kw-backend/blob/master/api/sync/WanikaniUserSyncerV2.py#L286The fix is to divorce the logic between sync and manual unlock. This must be a regression for the V2 syncer as this used to work.
The text was updated successfully, but these errors were encountered: