resolve irb crash issues #102
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://www.pivotaltracker.com/story/show/185815646
Problem Description: dry-rb/dry-logic#104
The presence of dry-logic version 1.2.0 is leading to a conflict with irb autocomplete functionality, resulting in crashes in the Rails console (rails console).Although the conflict has been addressed in dry-logic version 1.5.0, upgrading to this version is not feasible due to dependencies on event source dry gems.As a workaround, we are applying a monkey patch to the dry-logic gem to resolve the issueScreen.Recording.2023-08-11.at.11.34.06.AM.mov