Skip to content
This repository was archived by the owner on Oct 2, 2019. It is now read-only.

Fix tolerance for null or undefined values #1035

Closed
wants to merge 23 commits into from

Conversation

homerjam
Copy link
Contributor

fixes #967

@homerjam
Copy link
Contributor Author

Any chance of merging this?

@wesleycho
Copy link
Contributor

Changes to dist need to be removed, and this needs to be squashed and rebased.

@homerjam
Copy link
Contributor Author

Hi @wesleycho is there any chance you could help/explain how to go about this? I'm a bit of a casual git user 😊 (generally I use sourcetree - in case that helps?)

@wesleycho
Copy link
Contributor

In this case, git reset --hard a926f70; git pull --rebase origin master; git push -f should do the trick - do those commands separately though so you can step through things.

@homerjam
Copy link
Contributor Author

Thanks. Does the above look right?

@wesleycho
Copy link
Contributor

Looks like something was busted in the process - might be better to start fresh by killing the branch locally, updating master with current master, branch off and redo changes then force push up.

@homerjam homerjam closed this Mar 27, 2016
@homerjam homerjam deleted the patch-1 branch March 27, 2016 18:20
@homerjam
Copy link
Contributor Author

I made a mistake and deleted my branch - have resubmitted here

user378230 added a commit to user378230/ui-select that referenced this pull request Jul 7, 2016
user378230 added a commit to user378230/ui-select that referenced this pull request Jul 7, 2016
Previously view value was checked and corrected if undefined, but then
overwritten with the invalid value again.

This is a minor commit to ensure the updated value isn't overwritten
again.

Originally authored by homerjam

Closes angular-ui#967 and angular-ui#1686
Supersedes angular-ui#1035 angular-ui#1529 angular-ui#1687
user378230 added a commit that referenced this pull request Jul 7, 2016
Previously view value was checked and corrected if undefined, but then
overwritten with the invalid value again.

This is a minor commit to ensure the updated value isn't overwritten
again.

Originally authored by homerjam

Closes #967 and #1686
Supersedes #1035 #1529 #1687
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.

Possible error with ngModel.$render with null/undefined values
6 participants