Editor editor = new Editor(pomDocument);
        Element root = editor.root();
        if (root == null) {
            return;
        }

        Element modelVersionElement = root.child(MODEL_VERSION).orElse(null);
        if (modelVersionElement != null) {
            editor.setTextContent(modelVersionElement, newVersion);
        } else {

    var editor: DiskLruCache.Editor? = null
    try {
      editor = snapshot.edit() ?: return // edit() returns null if snapshot is not current.
      entry.writeTo(editor)
      editor.commit()
    } catch (_: IOException) {
      abortQuietly(editor)
    }
  }

  private fun abortQuietly(editor: DiskLruCache.Editor?) {
    // Give up because the cache cannot be written.

    id: expected-behavior
    attributes:
      label: "What did you expect to see?"
    validations:
      required: true
  - type: textarea
    id: editor-and-settings
    attributes:
      label: "Editor and settings"
      description: "Your editor and any settings you have configured (for example, your VSCode settings.json file)"
    validations:
      required: false
  - type: textarea
    id: logs
    attributes:

```

as in:

{* ../../docs_src/body_nested_models/tutorial008_py310.py hl[13] *}

## Editor support everywhere { #editor-support-everywhere }

And you get editor support everywhere.

Even for items inside of lists:

<img src="/img/tutorial/body-nested-models/image01.png">

You couldn't get this kind of editor support if you were working directly with `dict` instead of Pydantic models.

```

so wie in:

{* ../../docs_src/body_nested_models/tutorial008_py310.py hl[13] *}

## Editor-Unterstützung überall { #editor-support-everywhere }

Und Sie erhalten Editor-Unterstützung überall.

Selbst für Dinge in Listen:

<img src="/img/tutorial/body-nested-models/image01.png">

Sie würden diese Editor-Unterstützung nicht erhalten, wenn Sie direkt mit `dict`, statt mit Pydantic-Modellen arbeiten würden.

{* ../../docs_src/body_nested_models/tutorial008_py310.py hl[13] *}

## Her yerde editör desteği { #editor-support-everywhere }

Ve her yerde editör desteği alırsınız.

List içindeki öğeler için bile:

<img src="/img/tutorial/body-nested-models/image01.png">

Pydantic modelleri yerine doğrudan `dict` ile çalışsaydınız bu tür bir editör desteğini alamazdınız.

        return xml.toString();
    }

    public Document buildDocument() {
        try {
            String xmlContent = build();
            Editor editor = new Editor(Document.of(xmlContent));
            return editor.document();
        } catch (Exception e) {
            throw new RuntimeException("Failed to build POM document", e);
        }
    }

<img src="/img/tutorial/body/image05.png">

/// tip | İpucu

Editor olarak [PyCharm](https://www.jetbrains.com/pycharm/) kullanıyorsanız, [Pydantic PyCharm Plugin](https://github.com/koxudaxi/pydantic-pycharm-plugin/) kullanabilirsiniz.

Pydantic modelleri için editor desteğini şu açılardan iyileştirir:

* auto-completion

{* ../../docs_src/body_nested_models/tutorial008_py310.py hl[13] *}

## Suporte de editor em todo canto { #editor-support-everywhere }

E você obtém suporte do editor em todos os lugares.

Mesmo para itens dentro de listas:

<img src="/img/tutorial/body-nested-models/image01.png">

Você não conseguiria este tipo de suporte de editor se estivesse trabalhando diretamente com `dict` em vez de modelos Pydantic.

            // Verify the model version and namespace - use the updated document from pomMap
            Document updatedDocument = pomMap.get(Paths.get("pom.xml"));
            Editor editor = new Editor(updatedDocument);
            Element root = editor.root();
            assertEquals(expectedNamespace, root.namespaceURI(), "Namespace should be updated: " + description);