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: never wrap unless at_edge is set to wrap #171

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

thenbe
Copy link
Contributor

@thenbe thenbe commented Mar 27, 2024

fixes #170


In the future, there might room for further refactoring by collapsing the two consecutive if statements.

-  if multiplexer_moved or not will_wrap then
+  if multiplexer_moved or at_edge ~= AtEdgeBehavior.wrap then
     return multiplexer_moved
   end

This would also mean that will_wrap no longer needs to be passed to this function in the first place.

@mrjones2014 mrjones2014 merged commit a0d40cb into mrjones2014:master Mar 28, 2024
2 checks passed
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.

[Bug]: wrapping occurs despite setting at_edge to a value other than wrap
2 participants