Allow Validators/Excluders to store info on an individual stage use..

Created on 23 December 2022, over 1 year ago
Updated 2 March 2023, over 1 year ago

Problem/Motivation

We want to make them aware of the stage being handled, basically if the stage they were operating on was changed and maybe it would also be good to know if the stage it was working on was destroyed.

The need for it came up while working on 🐛 GitExcluder should not ignore .git directories that belong to packages installed by Composer Fixed as we wanted to know if a stage was destroyed in between the subscribed events calls we ended up using the preCreate and postDestroy event to know when the stage was created and destroyed.

Steps to reproduce

Proposed resolution

1 possible solution would be to make \Drupal\package_manager\Stage::getMetadata and \Drupal\package_manager\Stage::setMetadata public

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Closed: outdated

Version

3.0

Component

Code

Created by

🇮🇳India omkar.podey

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024