Interceptors can be chained. Suppose you have both a compressing interceptor and a checksumming interceptor: you'll need to decide whether data is compressed and then checksummed, or checksummed and then compressed. OkHttp uses lists to track interceptors, and interceptors are called in order.

![Interceptors Diagram](../assets/images/******@****.***)

    val existingRouteSelection = routeSelection
    if (existingRouteSelection != null && existingRouteSelection.hasNext()) {
      return planConnectToRoute(existingRouteSelection.next())
    }

    // Decide which proxy to use, if any. This may block in ProxySelector.select().
    var newRouteSelector = routeSelector
    if (newRouteSelector == null) {
      newRouteSelector =
        RouteSelector(

        @Override
        public Integer getSuggestUpdateContentsLimitDocSizeAsInteger() {
            return 50000;
        }

        @Override
        public String getIndexFieldDocId() {
            return "doc_id";
        }

        @Override
        public String getIndexFieldClickCount() {
            return "click_count";
        }

        @Override
        public String getIndexDocumentSearchIndex() {

                    <version>1.0.0</version>
                </project>
                """;

            Document doc1 = Document.of(pomXml);
            Document doc2 = Document.of(pomXml);

            Map<Path, Document> pomMap = new HashMap<>();
            pomMap.put(Paths.get("/project/pom1.xml"), doc1);
            pomMap.put(Paths.get("/project/pom2.xml"), doc2);

            UpgradeContext context = createMockContext();

        when(mockSearchHits.getHits()).thenReturn(new SearchHit[] { mockHit }, new SearchHit[0]);
        when(mockHit.getIndex()).thenReturn("test-index");
        when(mockHit.getId()).thenReturn("doc1");

        // Setup scroll response (empty on second call)
        when(mockClient.prepareSearchScroll("scroll1")).thenReturn(mockScrollBuilder);

        SuggestItem[] items = new SuggestItem[3];

        // Document only
        String[][] readings1 = new String[1][];
        readings1[0] = new String[] { "doc1" };
        items[0] = new SuggestItem(new String[] { "ドキュメント1" }, readings1, new String[] { "content" }, 1, 0, -1, new String[] { "tag1" },

            @Override
            public String getIndexFieldId() {
                return "_id";
            }

            @Override
            public String getIndexFieldDocId() {
                return "doc_id";
            }

            @Override
            public String getIndexFieldBoost() {
                return "boost";
            }

            @Override

     * an object type argument, since in reflection
     * primitive type arguments are represented by
     * their object counterparts, so for an argument of
     * type (say) java.lang.Integer, it will not be able
     * to decide between a method that takes int and a
     * method that takes java.lang.Integer as a parameter.
     * <p>
     * This turns out to be a relatively rare case
     * where this is needed - however, functionality

So, having a nice PR title will not only look nice in GitHub, but also in the release notes. 📝

## Add Labels to PRs

The same GitHub Action [latest-changes](https://github.com/tiangolo/latest-changes) uses one label in the PR to decide the section in the release notes to put this PR in.

Make sure you use a supported label from the [latest-changes list of labels](https://github.com/tiangolo/latest-changes#using-labels):

* `breaking`: Breaking Changes

        @Override
        public String getIndexDocumentUpdateIndex() {
            return "fess.update";
        }

        @Override
        public String getIndexFieldDocId() {
            return "doc_id";
        }

        @Override
        public String getIndexFieldId() {
            return "_id";
        }

        @Override
        public String getIndexFieldVersion() {