IBX-10827: Added option to extend ezpublish.rng schema

[ViniTou]

🎫 Issue	IBX-10827

Description:

• Adds extensibility for the RichText DocBook schema (ezpublish.rng) via semantic configuration
• Enables other bundles to register custom schema fragments that extend the base RichText validation schema
• Allows custom embed types to be added through configuration

Configuration Example

In a custom bundle's config

parameters:                                                                                                                                                                                                                                                                
    ibexa.field_type.richtext.docbook.schema_fragments:                                                                                                                                                                                                                    
        - '%kernel.project_dir%/src/Bundle/MyBundle/Resources/richtext/my_custom_elements.rng'                                                                                                                                                                             
                                                                                                                                                                                                                                                                           
ibexa:                                                                                                                                                                                                                                                                     
    system:                                                                                                                                                                                                                                                                
        default:                                                                                                                                                                                                                                                           
            fieldtypes:                                                                                                                                                                                                                                                    
                ezrichtext:                                                                                                                                                                                                                                                
                    embed:                                                                                                                                                                                                                                                 
                        product:  # Custom embed type                                                                                                                                                                                                                      
                            template: '@MyBundle/richtext/embed/product.html.twig'                                                                                                                                                                                         

How It Works

1. Schema fragments are registered via ibexa.field_type.richtext.docbook.schema_fragments parameter
2. A compiler pass generates a combined schema in cache, including base schema + fragments
3. Extension points (ez.extension.blocks, ez.extension.inlines) are made combinable via combine="choice"
4. Custom embed types require a template key in configuration

Example output rng

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
       xmlns:db="http://docbook.org/ns/docbook"
       xmlns:ez="http://ibexa.co/xmlns/ezpublish/docbook"
       xmlns:ezxhtml="http://ibexa.co/xmlns/dxp/docbook/xhtml"
       xmlns:ezcustom="http://ibexa.co/xmlns/dxp/docbook/custom"
       xmlns:xlink="http://www.w3.org/1999/xlink"
       ns="http://docbook.org/ns/docbook"
       datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">

<include href="/var/www/html/vendor/ibexa/fieldtype-richtext/src/bundle/Resources/richtext/schemas/docbook/ezpublish.rng">
  <!-- Override extension points to make them combinable if they are not already -->
  <define name="ez.extension.blocks" combine="choice">
    <notAllowed/>
  </define>
  <define name="ez.extension.inlines" combine="choice">
    <notAllowed/>
  </define>
</include>
<include href="/var/www/html/vendor/ibexa/product-catalog/src/bundle/Resources/richtext/schemas/docbook/product_elements.rng"/>

</grammar>

For QA:

Documentation:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[konradoboza]

Suggested change

	final class RichTextDocbookSchemaPass implements CompilerPassInterface
	final readonly class RichTextDocbookSchemaPass implements CompilerPassInterface

[konradoboza]

Is this needed if CompilerPass fallbacks to an empty array?

[konradoboza]

Aren't those permissions too forgiving? Maybe after saving the file we should change those to 644. It just raises an eyebrow when looking at "7" passed as permission.