Add an ajaxEnabled() method for ViewExecutable

+++ b/core/modules/views/lib/Drupal/views/Tests/Plugin/PagerTest.phpundefined
@@ -250,7 +250,8 @@ public function testRenderNullPager() {
+    // force the value again here.

Let's "Force" it :)

+++ b/core/modules/views/lib/Drupal/views/Tests/Plugin/PagerTest.phpundefined
@@ -250,7 +250,8 @@ public function testRenderNullPager() {
+    $view->setUseAJAX(TRUE);

Should be better setUsesAJAX?

+++ b/core/modules/views/lib/Drupal/views/ViewExecutable.phpundefined
@@ -67,7 +67,7 @@ class ViewExecutable {
+  public $usesAJAX = FALSE;

What about making it protected now?

+++ b/core/modules/views/lib/Drupal/views/ViewExecutable.phpundefined
@@ -545,8 +545,19 @@ public function usePager() {
    * rather than a page refresh.

What about documenting the parameter as boolean?

+++ b/core/modules/views/lib/Drupal/views/ViewExecutable.phpundefined
@@ -545,8 +545,19 @@ public function usePager() {
+   * @see setUseAJAX().

I guess we should use ViewExecuteable::setUsesAJAX here (maybe even with full namespace).

It adds test coverage, has proper documentation etc.

PS: you could nitpick $use_ajax -> $uses_ajax

Perfect, thank you for all the small changes!

setUseAjax() and setUsesAjax() are strange method names. Could it be at least get/set? Is 'uses' the best word here?

+++ b/core/modules/views/lib/Drupal/views/ViewExecutable.phpundefined
@@ -549,19 +549,19 @@ public function usePager() {
+  public function ajaxEnabled() {
+    return $this->ajaxEnabled;
   }

To be honest, it's confusing to both have isAJAXEnabled on the display but also AjaxEnabled, at least we should use AJAXEnabled, but i really vote for more consistency. Either the view or the display uses ajax. This seems not to be rocket science.

Oh didn't we agreed in Paris to always use uppercase for shortcuts?

Okay, so this looks good now!

There's an issue somewhere about ajax vs. AJAX in method names, I prefer the latter (at least when it's something like testCss() which just looks silly), but I think at the moment it's just camel case in core.

Committed/pushed this to 8.x.