Repository navigation
fix(actor-memory-expression): only resolve own properties in get() - #730
Merged
Merged
Conversation
The `get()` helper in memory expressions followed inherited properties too, so a path like `constructor` or `toString` resolved to a built-in function instead of falling back to the default value. It now only follows own properties. `length` on arrays and strings still works.
B4nan
added
adhoc
apify-service-account
added
the
tested
janbuchar
approved these changes
Nov 6, 2026
This was referenced Nov 6, 2026
l2ysho
pushed a commit
to apify/apify-cli
that referenced
this pull request
Nov 7, 2026
Picks up the `get()` fix in memory expressions from apify/apify-shared-js#730.
Pijukatel
pushed a commit
to apify/actor-runtime
that referenced
this pull request
Nov 9, 2026
Picks up the `get()` fix in memory expressions from apify/apify-shared-js#730.
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
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.
The
get()helper in memory expressions followed inherited properties too, so a path likeconstructorortoStringresolved to a built-in function instead of falling back to the default value. It now only follows own properties.lengthon arrays and strings still works.