A downside of this structure is that it is difficult to do focused work on the Gradle UI.

## Decision

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.

    },
    listDeselectedCssInfo: {
      "background-color": "#ffffff"
    },
    minterm: 1,
    adjustWidthVal: 11,
    searchForm: $("#searchForm")
  };

  $("#contentQuery").focus();

  $("#searchForm").on("submit", function() {
    $searchButton.prop("disabled", true);
    var $icon = $searchButton.find("i.fa-search");
    if ($icon.length > 0) {

- **Base class**: Extend `PlainTestCase` from UTFlute
- **Test Resources**: `src/test/resources/`
- **Coverage Goal**: >80% line coverage

### Contributing

1. Fork repo, create feature branch
2. Make focused commits with tests
3. Format code (`mvn formatter:format && mvn license:format`)
4. Run tests (`mvn test`)
5. Open Pull Request

---

## Quick Reference

### Key File Locations

## First Steps { #first-steps }

Let's see a very simple example. It will be so simple that it is not very useful, for now.

But this way we can focus on how the **Dependency Injection** system works.

### Create a dependency, or "dependable" { #create-a-dependency-or-dependable }

Let's first focus on the dependency.

It is just a function that can take all the same parameters that a *path operation function* can take:

## Context

The Gradle code base is essentially a large monolith, without strong internal boundaries.
This has a number of negative effects on productivity, including:

- Unclear ownership of code.
- Difficult to focus on one particular area.
- Unintended coupling between areas of the code, including tests.

## Decision

Organize the Gradle code base into a set of coarse-grained "architecture modules".

This, of course, is not optimal and you wouldn't use it for production.

In production you would have one of the options above.

But it's the simplest way to focus on the server-side of WebSockets and have a working example:

{* ../../docs_src/websockets_/tutorial001_py310.py hl[2,6:38,41:43] *}

## Create a `websocket` { #create-a-websocket }

            updateUI();
            showStatus('ready');
            hideProgressIndicator();
            eventSource.close();
            scrollToBottom();

            // Focus back to input
            elements.chatInput.focus();
        });

        eventSource.addEventListener('error', function(e) {
            state.errorHandled = true;
            var errorMessage = config.labels.error;
            try {

/// tip

In the next chapter, you will see a real secure implementation, with password hashing and <abbr title="JSON Web Tokens">JWT</abbr> tokens.

But for now, let's focus on the specific details we need.

///

{* ../../docs_src/security/tutorial003_an_py310.py hl[87] *}

/// tip

But then, the project's focus shifted.

It was no longer an API web framework, as the creator needed to focus on Starlette.

Now APIStar is a set of tools to validate OpenAPI specifications, not a web framework.

/// info

import org.opensearch.index.query.TermQueryBuilder;
import org.opensearch.index.query.functionscore.FunctionScoreQueryBuilder;

/**
 * Tests for SuggestRequest query building methods.
 * These tests focus on the buildQuery, buildFilterQuery, and buildFunctionScoreQuery methods.
 */
public class SuggestRequestQueryBuildingTest {

    private TestableSuggestRequest request;

    @Before
    public void setUp() {