Skip to content

Add integration for Drupal#1

Open
marcospassos wants to merge 4 commits into
masterfrom
initial-implementation
Open

Add integration for Drupal#1
marcospassos wants to merge 4 commits into
masterfrom
initial-implementation

Conversation

@marcospassos

Copy link
Copy Markdown
Member

Summary

Drupal integration is a thin layer on top of the Symfony integation.

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

@marcospassos marcospassos added the feature New feature label Jun 6, 2026
Replace the local `path` repositories for croct/plug-php and
croct/plug-symfony with `vcs` repositories pointing at their GitHub
repos, so CI can resolve `dev-initial-version` / `dev-initial-implementation`
from the pushed branches instead of sibling directories that only exist
locally. The path repos broke `composer install` in the composer, test,
validate, and lint jobs, and left the committed lock incompatible with
composer.json.

Regenerate the lock against the git sources. Resolving plug-symfony via
vcs additionally required correcting the package name on the
symfony-bundle-php master branch (done separately), since Composer
derives a repository's package name from its default branch.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Comment on lines +23 to +25
if ($response instanceof CacheableResponseInterface) {
$response->getCacheableMetadata()->addCacheContexts(['session']);
}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[NOTE] Won't this still allow (even if not enforce, depends on surrounding config) Drupal to cache the request for the user so subsequent fetches to the same slot might not get updated with new event information?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants