Skip to content

chore(benchmarks): use isSupported() rather than !isJsObject()#2995

Closed
caitp wants to merge 1 commit into
angular:masterfrom
caitp:benchmarker
Closed

chore(benchmarks): use isSupported() rather than !isJsObject()#2995
caitp wants to merge 1 commit into
angular:masterfrom
caitp:benchmarker

Conversation

@caitp
Copy link
Copy Markdown
Contributor

@caitp caitp commented Jul 11, 2015

Seems more accurate, and would allow isJsObject() to handle typical
{}-literals in dart, which could be useful

Seems more accurate, and would allow `isJsObject()` to handle typical
`{}`-literals in dart, which could be useful
@caitp
Copy link
Copy Markdown
Contributor Author

caitp commented Jul 13, 2015

@vsavkin does this approach seem more reasonable than testing isJsObject()? I wanted the dart facade to support isJsObject in order to deal with dart object literals a bit better (or maybe it should just handle JsObject subclasses, but hey)

@caitp caitp closed this in e1e7912 Jul 14, 2015
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants