Fix/correcting branches#37
Merged
Merged
Conversation
Updated roadmap and README
Allows end-users to import less modules
* Refactored logging module for better organization
* Moved it into "nodeEnterTree" instead of "nodeReady" * Also made context provide lambdas, so calling "provide" calls the up to date value
GuilhermeF03
added
operations
This file contains hidden or 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
2 participants
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.
What does this PR do, and why
This PR aims to fix the mess left by both the release/0.1.0, the feature branch created from that, and mixed commits. All of this makes working with other people more complex than needed.
What changes were made
Cherry picked commits from 31-colored-console-logs-bleeding-into-files that don't involve logging. This way the main branch will have all the current changes, and the respective logging changes will then come from the 31
Note
We probably need to create a branch that comes from main, and cherry pick the commits with logging into that. This way there won't be conflicts on the already merged changes from 'fix/correcting-branches'.
Type of Change
Checklist