This repository has been archived by the owner on Sep 1, 2021. It is now read-only.
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.
I backported the
this
expression that I introduced to construct3 (which I don't have time to finish). So I decided it would be a good idea to backport it. It's 100% backwards compatible, so there's no harm whatsoever, and it's much more readable and concise than those ugly lambdas.In short:
Field(..., lambda ctx: ctx.length)
useField(..., this.length)
Field(..., lambda ctx: ctx._.length * 4)
useField(..., this._.length * 4)
If(lambda ctx: ctx["foo"] > 17, ...)
, useIf(this.foo > 17, ...)
I included a unit test (
tests/test_this.py
).By the way, I would suggest moving the tests directory out of the package, e.g.