Use new {tinkr} method $get_protected()
#155
Draft
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
Only testing on CI because there are weird SSL issues popping up that makes it slower than molases
I don't _believe_ than anything has failed, but i want to make sure.
This will allow us to move forward with the `$get_protected()` method
so that {tinkr} can implement more control over protected and
unprotected nodes without needing to constantly split nodes.
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.
This PR will do three things:
with the current version of {pegboard}
$get_protected()method to prepare for changes coming in{tinkr} 1.0.0.
get_lesson()on CI to avoid weird SSL issues in tests (which otherwise work fine interactively).