Você provavelmente leu anteriormente que você pode definir um [Código de Status do Retorno](../tutorial/response-status-code.md){.internal-link target=_blank} padrão.

Porém em alguns casos você precisa retornar um código de status diferente do padrão.

## Caso de uso { #use-case }

Por exemplo, imagine que você deseja retornar um código de status HTTP de "OK" `200` por padrão.

  static void checkCast(Class<?> clazz, Object obj) {}

  static <T> T[] clone(T[] array) {
    return (T[]) Arrays.copyOfRange(array, 0, array.length);
  }

  // TODO: Consolidate different copies in one single place.
  static String format(String template, Object... args) {
    // start substituting the arguments into the '%s' placeholders

        int level = (int) levelField.get(msrpcShareEnum);
        assertEquals(1, level);
    }

    @Test
    void testShareTypeTransformation() throws Exception {
        // Test different share types and their transformations
        // Type 0 (disk share) -> TYPE_SHARE (8)
        srvsvc.ShareInfo1 diskShare = new srvsvc.ShareInfo1();
        diskShare.netname = "DiskShare";
        diskShare.type = 0;

    }

    @Test
    void testLoadBalancingStrategies() throws Exception {
        // Test different load balancing strategies
        ChannelLoadBalancer loadBalancer = new ChannelLoadBalancer(channelManager);

        // Test setting different strategies
        LoadBalancingStrategy[] strategies = { LoadBalancingStrategy.ROUND_ROBIN, LoadBalancingStrategy.LEAST_LOADED,

 * error codes, constants and text messages like "The device is not ready"
 * are provided.
 * <p>
 * The jCIFS client maps DOS error codes to NTSTATUS codes. This means that
 * the user may receive a different error from a legacy server than that of
 * a newer variant such as Windows NT and above. If you should encounter
 * such a case, please report it to jcifs at samba dot org and we will
 * change the mapping.
 */

import junit.framework.TestCase;
import junit.framework.TestSuite;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests our AtomicHelper fallback strategies in AbstractFuture.
 *
 * <p>On different platforms AbstractFuture uses different strategies for its core synchronization
 * primitives. The strategies are all implemented as subtypes of AtomicHelper and the strategy is

            assertTrue(merged.errorPoms().contains(pom2), "Should contain failed POM");
        }

        @Test
        @DisplayName("should handle merging with different POM sets")
        void shouldHandleMergingWithDifferentPOMSets() {
            Path pom1 = Paths.get("pom.xml");
            Path pom2 = Paths.get("module1/pom.xml");
            Path pom3 = Paths.get("module2/pom.xml");

For example:

{* ../../docs_src/metadata/tutorial001_1_py39.py hl[31] *}

## Metadata for tags { #metadata-for-tags }

You can also add additional metadata for the different tags used to group your path operations with the parameter `openapi_tags`.

It takes a list containing one dictionary for each tag.

Each dictionary can contain:

	// TargetStrip > 0 we strip the left most TargetStrip labels from the
	// DNS name.
	TargetStrip int `json:"targetstrip,omitempty"`

	// Group is used to group (or *not* to group) different services
	// together. Services with an identical Group are returned in
	// the same answer.
	Group string `json:"group,omitempty"`

	// Key carries the original key used during Put().
	Key string `json:"-"`

- **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.

## Decision

We do not introduce new public API methods that include Groovy types in their signatures.
Existing Groovy methods will not be removed immediately.

## Status

ACCEPTED