Apply the latest XP changes 8 #9266

[anatol-sialitski]

save changes

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 142).

The issue identified by the Checkstyle linter is that the line of code exceeds the maximum allowed length of 140 characters, which can reduce readability and maintainability. To resolve this, we can break the long line into two shorter lines while ensuring that the code remains functional and clear.

Here's the suggested single line change to fix the issue:

Suggested change

	.schemaConfig( GenericValue.object().put( "listTitleExpression", "${data.val1} ${missing} ${data.val1} ${displayName}" ).build() )
	.schemaConfig( GenericValue.object().put( "listTitleExpression", "${data.val1} ${missing} ${data.val1} ${displayName}" )

This change wraps the method call in a way that allows it to fit within the character limit without altering the logic of the code.

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 144).

The issue identified by the Checkstyle linter is that the line exceeds the maximum allowed length of 140 characters, which can make the code harder to read and maintain. To resolve this, we can break the line into multiple lines while ensuring that the code remains clear and properly formatted.

Here’s a code suggestion that addresses the issue by breaking the line into a more manageable length:

                MixinMapping.create().mixinName(descriptor.getName())
                    .allowContentTypes("app:testContentType")
                    .optional(false)
                    .build() ) )

This change maintains the functionality of the code while adhering to the style guidelines.

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 142).

The issue identified by the Checkstyle linter is that the line exceeds the maximum allowed length of 140 characters, which can make the code harder to read and maintain. To resolve this, we can break the line into two or more lines to adhere to the coding style guidelines.

Here's a code suggestion that addresses the issue by breaking the line after the first addFormItem call:

            addFormItem( Input.create().name( "myTextLine" ).label( "myTextLine" ).inputType( InputTypeName.TEXT_LINE ).build() )
                .addFormItem(

This change ensures that the line length is within the acceptable limit while maintaining the readability of the code.

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 142).

The issue identified by the Checkstyle linter is that the line in question exceeds the maximum allowed length of 140 characters, which can hinder readability and maintainability of the code.

To resolve this issue, we can break the line into two parts by moving the closing parenthesis of the filter method to a new line. This keeps the line length within the specified limit while maintaining the logical structure of the code.

Here's the suggested change:

Suggested change

	.filter( type -> type.getSchemaConfig().optional( "allowNewContent").map( GenericValue::asBoolean ).orElse( Boolean.TRUE ) ) )
	.filter( type -> type.getSchemaConfig().optional( "allowNewContent").map( GenericValue::asBoolean ).orElse( Boolean.TRUE ))

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 177).

The issue reported by the Checkstyle linter indicates that the line exceeds the maximum allowed length of 140 characters, which can impact readability and maintainability of the code. To resolve this, we can break the line into multiple lines while ensuring that the code remains clear and functional.

Here's a single line change that addresses the issue by breaking the line into two parts:

            SiteDescriptor.create().applicationKey(ApplicationKey.from("myapplication"))
                .mappingDescriptors(ControllerMappingDescriptors.from(mapingDescriptor)).build();

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 171).

The issue identified by the Checkstyle linter is that the line exceeds the maximum allowed length of 140 characters, making it less readable and harder to maintain. Long lines can be difficult to navigate and may not fit well in standard code editors, which can lead to poor readability.

To resolve this issue, we can break the long line into multiple lines for better readability while keeping the code functional. Here's a suggested change that maintains the original logic but adheres to the line length constraint:

                                                                                                                            GenericValue.object().put( "value", "notTranslatedValue" )
                                                                                                                                .put( "label", GenericValue.object().put( "i18n", "translate.option" ).build() ).build() ).build();

This change breaks the line at a logical point, making it more manageable and ensuring it stays within the character limit.

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 177).

The issue reported by the Checkstyle linter is that the line of code exceeds the maximum allowed length of 140 characters, which can make it difficult to read and maintain. To resolve this, we can break the line into two parts by moving the method call mappingDescriptors(...) to a new line, while ensuring proper indentation for clarity.

Here's the suggested change:

            SiteDescriptor.create().applicationKey( ApplicationKey.from( "myapplication" ) )
                .mappingDescriptors( ControllerMappingDescriptors.from( mapingDescriptor ) ).build();

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 194).

The issue reported by the Checkstyle linter is that the line where siteDescriptor is being created exceeds the maximum allowed length of 140 characters, which makes the code less readable and harder to maintain. To resolve this, we can break the line into multiple lines while ensuring that it remains clear and follows the coding conventions.

Here’s a suggested change that keeps the method calls aligned and improves readability without exceeding the character limit:

        final SiteDescriptor siteDescriptor = SiteDescriptor.create()
            .applicationKey(ApplicationKey.from("myapplication"))
            .mappingDescriptors(ControllerMappingDescriptors.empty())
            .build();

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 142).

The issue identified by the Checkstyle linter is that the line of code exceeds the maximum allowed length of 140 characters, which can make the code harder to read and maintain. To resolve this, we can break the line into two parts, while still keeping it as a single logical statement.

Here’s a code suggestion to fix the issue:

            String result = request().path("cms/default/content/schema/mixins/getContentMixins")
                                    .queryParam("contentId", "contentId").get().getAsString();

---

This comment was generated by an experimental AI tool.

[codacy-production]

ℹ️ Codacy found a minor CodeStyle issue: Line is longer than 140 characters (found 147).

The issue identified by the Checkstyle linter is that the line in question exceeds the maximum allowed length of 140 characters, which can affect readability and maintainability of the code.

To resolve this, we can break the line into two separate lines while ensuring that the code remains clear and functional. The suggestion will involve adding a line break after the new LocaleMessageResolver( constructor call.

Here's the code suggestion:

                    new LocaleMessageResolver(localeService, mixinOption.mixinDescriptor().getName().getApplicationKey(), 
                        request.getLocales()) )

---

This comment was generated by an experimental AI tool.