- 🇳🇿New Zealand quietone
Thank you for the idea!
The proposal doesn't met the Criteria for evaluating proposed changes → . In this case, there is not demonstrated demand and support for the change.
Currently, many modules that define ajax routes use whatever paths they seem fit. For example: /block-category/autocomplete, /entity_reference_autocomplete/{target_type}/{selection_handler}/{selection_settings_key}, /contextual/render, /editor/{entity_type}/{entity}/{field_name}/{langcode}/{view_mode_id}, and so on.
This can sometimes make code inspection, debugging or DX as a whole unpleasant. Therefore I think that any route that returns response that is not a proper html page response but rather response designated for ajax calls(for example) should be placed to a specific path that would allow easy identification of the type of the response and module that is providing it.
For this reason I think these routes should be placed under /system/ajax/modulename/foobar. I mean this as Drupal code standard(that core would implement), not an absolute state that could be somehow restricted by the core.
Closed: works as designed
11.0 🔥
Last updated
Primarily changes documentation, not code. For Drupal core issues, select the Documentation component instead of using this tag. In general, component selection is preferred over tag selection.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Thank you for the idea!
The proposal doesn't met the Criteria for evaluating proposed changes → . In this case, there is not demonstrated demand and support for the change.