That information will be included in the generated OpenAPI and used by the documentation user interfaces and external tools.

/// note

Keep in mind that different tools might have different levels of OpenAPI support.

Some of them might not show all the extra information declared yet, although in most of the cases, the missing feature is already planned for development.

///

You can add a `title`:

        assertEquals(0x0101, SMBUtil.readInt2(paramBuffer, 2));
        assertEquals(0, SMBUtil.readInt2(paramBuffer, 4));
    }

    @DisplayName("Test with different information levels")
    @ParameterizedTest
    @CsvSource({ "4, 257", // FILE_BASIC_INFO -> 0x0101
            "5, 258", // FILE_STANDARD_INFO -> 0x0102
            "20, 260" // FILE_ENDOFFILE_INFO -> 0x0104
    })

    /**
     * Access to the file is sequential only
     */
    public static final int FILE_SEQUENTIAL_ONLY = 0x4;
    /**
     * File cannot be cached or buffered at intermediate levels
     */
    public static final int FILE_NO_IMTERMEDIATE_BUFFERING = 0x8;
    /**
     * All operations on the file are performed synchronously with alerts
     */

/// note

You don't necessarily need to add different scopes in different places.

We are doing it here to demonstrate how **FastAPI** handles scopes declared at different levels.

///

{* ../../docs_src/security/tutorial005_an_py310.py hl[5,141,172] *}

/// info | Technical Details

    }

    /**
     * Event severity levels
     */
    public enum Severity {
        INFO(0), WARNING(1), ERROR(2), CRITICAL(3);

        private final int level;

        Severity(int level) {
            this.level = level;
        }

                _src = _src.deferred;
                this.name = _src.dec_ndr_string();

            }
        }
    }

    /**
     * RPC message for retrieving server information at various detail levels
     */
    public static class ServerGetInfo extends DcerpcMessage {

        @Override
        public int getOpnum() {
            return 0x15;
        }

        /**

        SuggestUtil.createBulkLine("test_index", "_doc", item);
    }

    @Test
    public void testCreateBulkLineWithMultipleReadings() {
        // Test with multiple reading levels
        SuggestItem item = new SuggestItem(new String[] { "test" },
                new String[][] { { "reading1a", "reading1b" }, { "reading2a", "reading2b" }, { "reading3" } }, new String[] { "field1" }, 5,

     * Lanman compatibility level
     *
     * <a href="https://technet.microsoft.com/en-us/library/cc960646.aspx">Microsoft TechNet Documentation</a>
     *
     *
     * <table>
     * <caption>LM Compatibility Levels</caption>
     * <tr>
     * <td>0 or 1</td>
     * <td>LM and NTLM</td>
     * </tr>
     * <tr>
     * <td>2</td>
     * <td>NTLM only</td>
     * </tr>
     * <tr>
     * <td>3-5</td>

    Result (German):

        «««
        //// tab | Linux, macOS, Windows Bash
        Hallo wieder
        ////
        »»»


### Headings

Every Markdown heading in the English text (all levels) ends with a part inside curly brackets. This part denotes the hash of this heading, which is used in links to this heading. In translations, translate the heading, but do not translate this hash part, so that links do not break.

    Ordering<Number> unusedC = objects.compound(numbers);

    Ordering<Integer> unusedD = numbers.compound(integers);
    Ordering<Integer> unusedE = integers.compound(numbers);

    // This works with three levels too (IDEA falsely reports errors as noted
    // below. Both javac and eclipse handle these cases correctly.)

    Ordering<Number> unusedF = numbers.compound(objects).compound(objects); // bad IDEA