Skip to content
New issue

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

fix: crash without newest yazi #227

Merged
merged 1 commit into from
Jul 19, 2024
Merged

Conversation

mikavilpas
Copy link
Owner

There was a bug in opting in to the feature from 8114817 (feat: add targeted communication with the yazi instance (opt-in) (#225)). Even if you had not set use_yazi_client_id_flag = true in your config, the newest yazi was still required.

This commit fixes that bug by removing the passing of the yazi_id (roll forward style). Later changes can still utilize the feature and build on top of this.

There was a bug in opting in to the feature from 8114817 (feat: add
targeted communication with the yazi instance (opt-in) (#225)). Even if
you had not set `use_yazi_client_id_flag = true` in your config, the
newest yazi was still required.

This commit fixes that bug by removing the passing of the `yazi_id`
(roll forward style). Later changes can still utilize the feature and
build on top of this.
@mikavilpas mikavilpas enabled auto-merge (squash) July 19, 2024 09:42
@mikavilpas mikavilpas merged commit de4e79e into main Jul 19, 2024
14 checks passed
@mikavilpas mikavilpas deleted the fix-crash-without-newest-yazi branch July 19, 2024 09:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant