In your editor, inside your function you will get type hints and completion everywhere (this wouldn't happen if you received a `dict` instead of a Pydantic model):

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

You also get error checks for incorrect type operations:

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

This is not by chance, the whole framework was built around that design.

import model.Stage

class SanityCheck(
    model: CIBuildModel,
    stage: Stage,
) : OsAwareBaseGradleBuildType(os = Os.LINUX, stage = stage, init = {
        id(buildTypeId(model))
        name = "Sanity Check"
        description = "Static code analysis, checkstyle, release notes verification, etc."

        features {
            publishBuildStatusToGithub(model)
        }

        applyDefaults(
            model,

        assertNotNull(exception);
        assertEquals("Top level GSA error", exception.getMessage());

        // Check first level cause
        assertNotNull(exception.getCause());
        assertEquals("Intermediate problem", exception.getCause().getMessage());

        // Check second level cause
        assertNotNull(exception.getCause().getCause());

        // Assert: verify interaction and returned value
        verify(renewable, times(1)).renew();
        assertSame(returned, result, "renew() should return the stubbed value");

        // Negative interaction check: no further interactions with the mock
        verifyNoMoreInteractions(renewable);
    }

    @Test
    @DisplayName("Edge: calling renew() on a null reference throws NPE")
    void renewOnNullReferenceThrowsNPE() {

    e.trigger.classList.add("url-copied");
    e.trigger.classList.add("fas");
    e.trigger.classList.add("fa-check");
    setTimeout(function(){
      e.trigger.classList.remove("url-copied");
      e.trigger.classList.remove("fas");
      e.trigger.classList.remove("fa-check");
      e.trigger.classList.add("url-copy");
      e.trigger.classList.add("far");
      e.trigger.classList.add("fa-copy");

        // When
        int mode = response.getSecurityMode();

        // Then
        assertEquals(Smb2Constants.SMB2_NEGOTIATE_SIGNING_REQUIRED, mode);
    }

    @Test
    @DisplayName("Should check capability correctly")
    void testHaveCapability() throws Exception {
        // Given
        setPrivateField(response, "commonCapabilities", 0x2F); // 0010 1111

        // Then

	}

	// We know XFS already supports O_DIRECT no need to check.
	if fsType == "XFS" {
		return nil
	}

	// For all other FS pay the price of not using our recommended filesystem.

	// Check if backend is writable and supports O_DIRECT
	uuid := mustGetUUID()
	filePath := pathJoin(s.drivePath, minioMetaTmpDeletedBucket, ".writable-check-"+uuid+".tmp")

	// Create top level directories if they don't exist.

Most of these ideas would be more or less **independent**, and in most cases you should only need to study them if they apply directly to **your project**.

If something seems interesting and useful to your project, go ahead and check it, but otherwise, you might probably just skip them.

/// tip

    /**
     * Returns a new tree starting at this node, filtering the children.
     * Note that this node will not be filtered and only the children
     * and its descendant will be checked.
     *
     * @param filter the filter to apply
     * @return a new filtered graph
     */
    @Nonnull
    Node filter(@Nonnull Predicate<Node> filter);

    /**

    }

    @Override
    public String getName() {
        return netName;
    }

    @Override
    public int getType() {
        /* 0x80000000 means hidden but SmbFile.isHidden() checks for $ at end
         */
        switch (type & 0xFFFF) {
        case 1:
            return SmbFile.TYPE_PRINTER;
        case 3:
            return SmbFile.TYPE_NAMED_PIPE;
        }