Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More app code migration #5170

Merged
merged 3 commits into from
Jan 25, 2017
Merged

More app code migration #5170

merged 3 commits into from
Jan 25, 2017

Conversation

jwilander
Copy link
Member

Summary

Mostly just migrating functions, probably easier to review commit by commit.

Checklist

  • Added or updated unit tests (required for all new features)
  • Has enterprise changes (mattermost/enterprise#87)
  • Touches critical sections of the codebase (permissions, admin functions)

@jwilander jwilander added the 2: Dev Review Requires review by a developer label Jan 23, 2017
@coreyhulen coreyhulen added 4: Reviews Complete All reviewers have approved the pull request and removed 2: Dev Review Requires review by a developer labels Jan 25, 2017
@hmhealey hmhealey merged commit d245b29 into master Jan 25, 2017
@hmhealey hmhealey deleted the app-code-migration3 branch January 25, 2017 14:32
debanshuk pushed a commit to debanshuk/platform that referenced this pull request Feb 5, 2017
… which doens't exist.

This error is a side effect of changes done in PR mattermost#5181. In this PR logic to close response was added. But in cases when some error occures while getting the response, function to close response should not be called, as response is null in those cases.
Moreover, error was only occuring on the server and wasn't causing any error on the client until refactoring of code was done in PR mattermost#5170.
debanshuk pushed a commit to debanshuk/platform that referenced this pull request Feb 5, 2017
… which doens't exist.

This error was a side effect of changes done in PR mattermost#5181. In this PR logic to close response was added. But in cases when some error occurs while getting the response, function to close response should not be called, as response is null in those cases.
Moreover, error was only occurring on the server and wasn't causing any error on the client until refactoring of code was done in PR mattermost#5170.
debanshuk pushed a commit to debanshuk/platform that referenced this pull request Feb 5, 2017
…which don't exist.

This error was a side effect of changes done in PR mattermost#5181. In this PR logic to close response was added. But in cases when some error occurs while getting the response, function to close response should not be called, as response is null in those cases.
Moreover, error was only occurring on the server and wasn't causing any error on the client until refactoring of code was done in PR mattermost#5170.
debanshuk pushed a commit to debanshuk/platform that referenced this pull request Feb 6, 2017
…which don't exist.

This error was a side effect of changes done in PR mattermost#5181. In this PR logic to close response was added. But in cases when some error occurs while getting the response, function to close response should not be called, as response is null in those cases.
Moreover, the error was only occurring on the server and wasn't causing any error on the client until refactoring of code was done in PR mattermost#5170.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4: Reviews Complete All reviewers have approved the pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants