DigiComp.FlowTranslationEnd.../Configuration/Objects.yaml

DigiComp.FlowTranslationEndpoint:TranslationResponseCache:
  className: "Neos\\Cache\\Frontend\\StringFrontend"
  factoryObjectName: "Neos\\Flow\\Cache\\CacheManager"
  factoryMethodName: "getCache"
  arguments:
    1:
      value: "DigiComp_FlowTranslationEndpoint_Responses"

DigiComp.FlowTranslationEndpoint:TranslationRequestMiddleware:
  className: "DigiComp\\FlowTranslationEndpoint\\Http\\TranslationRequestMiddleware"
  autowiring: true
  arguments:
    1:
      setting: "DigiComp.FlowTranslationEndpoint.reactOnPath"
    2:
      setting: "DigiComp.FlowTranslationEndpoint.getParameterName"
    3:
      setting: "DigiComp.FlowTranslationEndpoint.browserCacheMaxAge"
    4:
      object: "Neos\\Flow\\I18n\\Service"
    5:
      object: "Neos\\Flow\\I18n\\Xliff\\Service\\XliffFileProvider"
    6:
      object: "Neos\\Flow\\I18n\\Detector"
    7:
      object: "DigiComp.FlowTranslationEndpoint:TranslationResponseCache"
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`DigiComp.FlowTranslationEndpoint:TranslationResponseCache:`
First version, extracted and tested 2023-08-05 15:49:46 +02:00			`className: "Neos\\Cache\\Frontend\\StringFrontend"`
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`factoryObjectName: "Neos\\Flow\\Cache\\CacheManager"`
			`factoryMethodName: "getCache"`
First version, extracted and tested 2023-08-05 15:49:46 +02:00			`arguments:`
			`1:`
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`value: "DigiComp_FlowTranslationEndpoint_Responses"`
First version, extracted and tested 2023-08-05 15:49:46 +02:00
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`DigiComp.FlowTranslationEndpoint:TranslationRequestMiddleware:`
			`className: "DigiComp\\FlowTranslationEndpoint\\Http\\TranslationRequestMiddleware"`
			`autowiring: true`
First version, extracted and tested 2023-08-05 15:49:46 +02:00			`arguments:`
			`1:`
As the tests shown, that the custom parameter breaks browser based caching, we now enforce the 'traditional url' approach and added cache control information for the browser 2023-08-08 17:02:13 +02:00			`setting: "DigiComp.FlowTranslationEndpoint.reactOnPath"`
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`2:`
As the tests shown, that the custom parameter breaks browser based caching, we now enforce the 'traditional url' approach and added cache control information for the browser 2023-08-08 17:02:13 +02:00			`setting: "DigiComp.FlowTranslationEndpoint.getParameterName"`
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`3:`
As the tests shown, that the custom parameter breaks browser based caching, we now enforce the 'traditional url' approach and added cache control information for the browser 2023-08-08 17:02:13 +02:00			`setting: "DigiComp.FlowTranslationEndpoint.browserCacheMaxAge"`
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`4:`
As the tests shown, that the custom parameter breaks browser based caching, we now enforce the 'traditional url' approach and added cache control information for the browser 2023-08-08 17:02:13 +02:00			`object: "Neos\\Flow\\I18n\\Service"`
First version, extracted and tested 2023-08-05 15:49:46 +02:00			`5:`
As the tests shown, that the custom parameter breaks browser based caching, we now enforce the 'traditional url' approach and added cache control information for the browser 2023-08-08 17:02:13 +02:00			`object: "Neos\\Flow\\I18n\\Xliff\\Service\\XliffFileProvider"`
			`6:`
			`object: "Neos\\Flow\\I18n\\Detector"`
			`7:`
review: consistent naming and methodology 2023-08-08 12:11:46 +02:00			`object: "DigiComp.FlowTranslationEndpoint:TranslationResponseCache"`