Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

refactor(filterFilter): simplify code by a ternary op instead of if-else #5637

Closed
wants to merge 1 commit into from

Conversation

royling
Copy link
Contributor

@royling royling commented Jan 5, 2014

  • use only one IIFE and a ternary op in it, instead of invoking separate IIFEs in if-else
    (this also completely fixed the same issue closed by PR fix(filter): filter on false properties #3597)
  • also add a spec to verify usage of '$' property in expression object (e.g. {$: 'a'})

- use only one IIFE and a ternary op in it, instead of invoking separate IIFEs in if-else
(this also completely fixed the same issue closed by PR angular#3597)
- also add a spec to verify usage of '$' property in expression object (e.g. `{$: 'a'}`)
@IgorMinar
Copy link
Contributor

thanks!

@IgorMinar IgorMinar closed this in e0ce9ed Jan 5, 2014
@ghost ghost assigned IgorMinar Jan 5, 2014
@royling royling deleted the refactor-2 branch January 11, 2014 09:14
jamesdaily pushed a commit to jamesdaily/angular.js that referenced this pull request Jan 27, 2014
- use only one IIFE and a ternary op in it, instead of invoking separate IIFEs in if-else
(this also completely fixed the same issue closed by PR angular#3597)
- also add a spec to verify usage of '$' property in expression object (e.g. `{$: 'a'}`)

Closes angular#5637
jamesdaily pushed a commit to jamesdaily/angular.js that referenced this pull request Jan 27, 2014
- use only one IIFE and a ternary op in it, instead of invoking separate IIFEs in if-else
(this also completely fixed the same issue closed by PR angular#3597)
- also add a spec to verify usage of '$' property in expression object (e.g. `{$: 'a'}`)

Closes angular#5637
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants