}

    /**
     * Add a message to the chat
     */
    function addMessage(role, content, streaming) {
        var avatarIcon = role === 'user' ? 'fa-user' : 'fa-robot';
        var timestamp = formatTimestamp(new Date());

        var html =
            '<div class="chat-message ' + role + '">' +
                '<div class="message-avatar"><i class="fa ' + avatarIcon + '" aria-hidden="true"></i></div>' +

        assertEquals("content", settings.array().get(SuggestSettings.DefaultKeys.SUPPORTED_FIELDS)[0]);
        assertEquals("label,virtual_host", settings.getAsString(SuggestSettings.DefaultKeys.TAG_FIELD_NAME, ""));
        assertEquals("role", settings.getAsString(SuggestSettings.DefaultKeys.ROLE_FIELD_NAME, ""));
    }

    @Test
    public void test_useExistenceSettings() {
        String indexName = "test";

## Submitting PRs

1. **Title and Summary**:
   - Use a scannable title: `[Subsystem] Action Description #Issue` (e.g., `[IAM] Add role-based access control #567`).
   - Include context in the summary: what changed, why, and any issue references.
   - Use `[WIP]` for in-progress PRs to avoid premature merging or choose GitHub draft PRs.

2. **Commits**:

/**
 * A facade that provides lifecycle services to components outside Maven core.
 *
 */
public interface LifecycleExecutor {

    // USED BY MAVEN HELP PLUGIN
    @Deprecated
    String ROLE = LifecycleExecutor.class.getName();

    // For a given project packaging find all the plugins that are bound to any registered
    // lifecycles. The project builder needs to now what default plugin information needs to be

                                        </button>
                                        <div class="modal fade" id="confirmToDelete"
                                             tabindex="-1" role="dialog">
                                            <div class="modal-dialog">
                                                <div class="modal-content bg-danger">

                                        </button>
                                        <div class="modal fade" id="confirmToDelete"
                                             tabindex="-1" role="dialog">
                                            <div class="modal-dialog">
                                                <div class="modal-content bg-danger">

									<li class="nav-item">
										<div class="dropdown">
											<a id="userMenu" class="nav-link dropdown-toggle" data-bs-toggle="dropdown"
												href="#" role="button" aria-haspopup="true" aria-expanded="false"
											> <i class="fa fa-fw fa-user" aria-hidden="true"></i>${username}
											</a>
											<div class="dropdown-menu" aria-labelledby="userMenu">

      },
      "location": {
        "type": "geo_point"
      },
      "mimetype": {
        "type": "keyword"
      },
      "parent_id": {
        "type": "keyword"
      },
      "role": {
        "type": "keyword"
      },
      "label": {
        "type": "keyword"
      },
      "virtual_host": {
        "type": "keyword"
      },
      "segment": {
        "type": "keyword"

            parameters {
                keepClassesByCoordinates = keepPatterns
            }
        }
    }
    afterEvaluate {
        // Without afterEvaluate, configurations.all runs before the configurations' roles are set.
        // This is yet another reason we need configuration factory methods.
        // workaround for https://github.com/gradle/gradle/issues/12459

Pour diffuser des JSON Lines avec FastAPI, au lieu d'utiliser `return` dans votre fonction de chemin d'accès, utilisez `yield` pour produire chaque élément à tour de rôle.

{* ../../docs_src/stream_json_lines/tutorial001_py310.py ln[1:24] hl[24] *}