id(buildTypeId(model) + suffix)
        name = "Smoke Ide Tests$suffix"
        description = "Tests against IDE sync process"

        applyTestDefaults(
            model = model,
            buildType = this,
            gradleTasks = ":smoke-ide-test:smokeIdeTest",
            extraParameters =
                listOf(

								styleClass="btn btn-outline-secondary btn-sm me-1 mb-1">${f:h(item)}</la:link>
						</c:forEach>
					</p>
				</div>
			</c:if>
		</div>
	</div>
	<div class="col-md-4"><%-- Side Content --%></div>

								styleClass="btn btn-outline-secondary btn-sm me-1 mb-1">${f:h(item)}</la:link>
						</c:forEach>
					</p>
				</div>
			</c:if>
		</div>
	</div>
	<div class="col-md-4"><%-- Side Content --%></div>

          if (data.result === "created") {
            var $favorited = $favorite.siblings(".favorited");
            var $favoritedCount = $(".favorited-count", $favorited);
            $favoritedCount.hide();
            $favorite.fadeOut(FADE_DURATION, function() {
              $favorited.fadeIn(FADE_DURATION);
            });
          }
        })
        .fail(function(jqXHR, textStatus, errorThrown) {

            includeModule("org.gradle.buildtool.internal", "configuration-cache-report")
            includeModule("org.gradle.buildtool.internal", "gradle-ide-starter")
            includeModule("org.gradle.buildtool.internal", "gradle-ide-starter-scenarios")
        }
    }
    google {
        content {
            includeGroup("com.android.databinding")

Although properties offer the benefit of precise user-side control and support gradual evolution practices, the high number of properties also presents challenges.

The main challenge on the user side is comprehensibility.

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading
* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers

name: IDE Experience team notifier
run-name: Notify the IDE Experience team about new RCs for manual testing
on:
  push:
    tags:
      - 'v*.*.*-RC1'

permissions: {}

jobs:
  send-slack-notification:
    runs-on: ubuntu-latest
    steps:
      - name: Send Slack notification about new RCs for manual testing
        id: slack
        uses: slackapi/slack-github-action@v3.0.1
        with:

    style core fill:#c2e0f4,stroke:#3498db,stroke-width:2px,color:#000;

    documentation["documentation module"]
    style documentation stroke:#1abc9c,fill:#b1f4e7,stroke-width:2px,color:#000;

    ide["ide module"]
    style ide stroke:#1abc9c,fill:#b1f4e7,stroke-width:2px,color:#000;

    subgraph software["software platform"]
    end
    style software fill:#c2e0f4,stroke:#3498db,stroke-width:2px,color:#000;
    software --> core

### Setup for OpenSearch Plugins

Run antrun:run to download plugins into the plugins directory:

    $ mvn antrun:run

### Run Fess

Run or debug org.codelibs.fess.FessBoot on your IDE, and then access http://localhost:8080/

### Build Package