The main feature I wanted from Django REST Framework was the automatic API documentation.

Then I found that there was a standard to document APIs, using JSON (or YAML, an extension of JSON) called Swagger.

And there was a web user interface for Swagger APIs already created. So, being able to generate Swagger documentation for an API would allow using this web user interface automatically.

labels.searchlog_requestedtime	=	Temps
labels.searchlog_accesstype	=	Type d'accès
labels.maintenance_title_configuration	=	Entretien
labels.number_of_shards_for_doc	=	Le nombre de fragments
labels.auto_expand_replicas_for_doc	=	Extension automatique des répliques
labels.clear_crawler_index	=	Indices de chenilles
labels.clear_crawler_index_button	=	Effacer les indices de chenilles
labels.diagnostic_logs	=	Diagnostique

  }

  public void testGetLast_withDefault_multiple() {
    Iterable<String> iterable = asList("foo", "bar");
    assertEquals("bar", Iterables.getLast(iterable, "qux"));
  }

  /**
   * {@link ArrayList} extension that forbids the use of {@link Collection#iterator} for tests that
   * need to prove that it isn't called.
   */
  private static class DiesOnIteratorArrayList extends ArrayList<String> {

	if newObjectLayerFn() == nil {
		return
	}

	// Disable server-side replication on object prefixes which are excluded
	// from versioning via the MinIO bucket versioning extension.
	if !globalBucketVersioningSys.PrefixEnabled(bucket, object) {
		return
	}

	replStatus := mopts.ReplicationStatus()
	if replStatus == replication.Replica && !mopts.isMetadataReplication() {
		return
	}

			// if we have a replication request
			// and SSE-S3 is specified do not preserve
			// the incoming etag.
			userDefined["etag"] = opts.PreserveETag
		}
	}

	// Guess content-type from the extension if possible.
	if userDefined["content-type"] == "" {
		userDefined["content-type"] = mimedb.TypeByExtension(path.Ext(object))
	}

	// if storageClass is standard no need to save it as part of metadata.

import org.junit.jupiter.api.AfterEach
import org.junit.jupiter.api.BeforeEach
import org.junit.jupiter.api.Tag
import org.junit.jupiter.api.Test
import org.junit.jupiter.api.Timeout
import org.junit.jupiter.api.extension.RegisterExtension

@Flaky // STDOUT logging enabled for test
@Timeout(30)
@Tag("Slow")
class EventListenerTest {
  @RegisterExtension
  val platform = PlatformRule()

  @RegisterExtension

La principale fonctionnalité que j'ai emprunté à Django REST Framework était la documentation automatique des API.

Puis j'ai découvert qu'il existait une norme pour documenter les API, en utilisant JSON (ou YAML, une extension de JSON) appelée Swagger.

Il existait déjà une interface utilisateur Web pour les API Swagger. Donc, être capable de générer une documentation

		}
		delete(userDefined, ReplicationSsecChecksumHeader)
	}

	// Initialize erasure metadata.
	for index := range partsMetadata {
		partsMetadata[index] = fi
	}

	// Guess content-type from the extension if possible.
	if userDefined["content-type"] == "" {
		userDefined["content-type"] = mimedb.TypeByExtension(path.Ext(object))
	}

	// if storageClass is standard no need to save it as part of metadata.

pkg crypto/x509/pkix, type RevokedCertificate struct, Extensions []Extension
pkg crypto/x509/pkix, type RevokedCertificate struct, RevocationTime time.Time
pkg crypto/x509/pkix, type RevokedCertificate struct, SerialNumber *big.Int
pkg crypto/x509/pkix, type TBSCertificateList struct
pkg crypto/x509/pkix, type TBSCertificateList struct, Extensions []Extension
pkg crypto/x509/pkix, type TBSCertificateList struct, Issuer RDNSequence

    - [Container Images](#container-images-16)
  - [Changelog since v1.26.0](#changelog-since-v1260)
  - [Known Issues](#known-issues)
    - [The PreEnqueue extension point doesn't work for Pods going to activeQ through backoffQ](#the-preenqueue-extension-point-doesnt-work-for-pods-going-to-activeq-through-backoffq)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)