Commit 436f2d70 authored by jamiewalch's avatar jamiewalch Committed by Commit bot

Remove AsyncResult::RESULT_FAILED_DIRECTORY. It's not used anywhere other than...

Remove AsyncResult::RESULT_FAILED_DIRECTORY. It's not used anywhere other than some code to communicate it to the webapp (where it's also not used).

Review URL: https://codereview.chromium.org/1687543004

Cr-Commit-Position: refs/heads/master@{#374837}
parent dea31689
......@@ -58,9 +58,6 @@ class DaemonController : public base::RefCountedThreadSafe<DaemonController> {
// TODO(sergeyu): Current implementations don't return this value.
RESULT_CANCELLED = 2,
// Failed to access host directory.
RESULT_FAILED_DIRECTORY = 3
// TODO(sergeyu): Add more error codes when we know how to handle
// them in the webapp.
};
......
......@@ -505,9 +505,6 @@ void Me2MeNativeMessagingHost::SendAsyncResult(
case DaemonController::RESULT_CANCELLED:
response->SetString("result", "CANCELLED");
break;
case DaemonController::RESULT_FAILED_DIRECTORY:
response->SetString("result", "FAILED_DIRECTORY");
break;
}
channel_->SendMessage(std::move(response));
}
......
......@@ -56,8 +56,7 @@ remoting.HostController.State.fromString = function(state) {
remoting.HostController.AsyncResult = {
OK: 0,
FAILED: 1,
CANCELLED: 2,
FAILED_DIRECTORY: 3
CANCELLED: 2
};
/**
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment