- 🇫🇷France dqd London | N.Y.C | Paris | Hamburg | Berlin
Haven't read yet over all comments but found parallel thougths of what brought me here in the intial issue summary point 1.) and in comment #3 or nod_ while I was fixing library.yml version issues in contrib modules.
What if we simply use the module version created by packaging script as /?version-path-suffix for library files and deprecate the tag for library files completely? Is that possible? (Drawback: no manual override possible then. But for what should that be needed?) This could be a solution for both, contrib and core (at least in my head)
- First commit to issue fork.
- Status changed to Needs review
9 months ago 11:19am 19 December 2024 - 🇮🇳India prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan
prem suthar → made their first commit to this issue’s fork.
- Merge request !10975Added the Mr with the Druapl 11 Updats also Added Mr Form Patch #38 suggestion of 40 . → (Open) created by prem suthar
- 🇮🇳India prem suthar Ahemdabad- Gujrat , Jodhpur - Rajsthan
Added the Mr with the Drupal 11 version with the some code updates and Added Mr Form Patch #38 as per the suggestion of 40 .
The Needs Review Queue Bot → tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.