Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(#542): remove deprecated version key from ddev dockerfile, upda… #694

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

BrianGilbert
Copy link
Member

@BrianGilbert BrianGilbert commented Jul 16, 2024

Summary by CodeRabbit

  • New Features

    • Added new dependencies and updated versions of various Drupal core packages and contributed modules.
    • Introduced new configuration settings for mail notification, session cookie name uniqueness, and state caching.
  • Improvements

    • Updated revision and logging configurations for various block content and system settings.
    • Enhanced pagination settings across multiple views configurations.
  • Bug Fixes

    • Adjusted image upload settings and fixed outdated URLs in several configuration files.
    • Removed obsolete module references and configuration fields.
  • Documentation

    • Improved comments and documentation blocks in configuration files for better clarity and security.

…te core and contrib/config, disable deprecated sdc module
Copy link

changeset-bot bot commented Jul 16, 2024

⚠️ No Changeset found

Latest commit: a21cb35

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

coderabbitai bot commented Jul 16, 2024

Walkthrough

The changes predominantly consist of configuration updates for a Drupal project, including version updates, dependency additions, and setting adjustments across various configuration files. Key modifications involve updating the revision and logging configurations, adjusting field values to null, and adding pagination settings. There's also the introduction of new parameters and removal of outdated URLs.

Changes

File Path Change Summary
docs/drupal/.ddev/docker-compose.env.yaml Removed the version key and its value '3.6'.
docs/drupal/composer.json Updated Drupal core package versions and added new dependencies.
docs/drupal/config/sync/block_content.type...yml Changed revision field values from 0 to false in multiple block content configuration files.
docs/drupal/config/sync/core.extension.yml Removed the sdc module entry.
docs/drupal/config/sync/editor.editor...yml Modified image upload settings and max_size field values.
docs/drupal/config/sync/jsonapi.settings.yml Removed langcode field from the _core section.
docs/drupal/config/sync/language/es/views...yml Added labels, descriptions, and display titles for related recipes.
docs/drupal/config/sync/node.type...yml Updated help field values from an empty string to null in multiple node type configuration files.
docs/drupal/config/sync/system...yml Updated logging field from 1 to true and country field default value from empty string to null.
docs/drupal/config/sync/taxonomy.vocabulary...yml Added new_revision field with false value.
docs/drupal/config/sync/views.view...yml Added pagination_heading_level: h4 to various view configuration files.
docs/drupal/web/autoload.php Removed reference to core/modules/statistics/statistics.php from the documentation block.
docs/drupal/web/sites/default/default.services.yml Introduced new parameters security.enable_super_user and name_suffix.
docs/drupal/web/sites/default/default.settings.php Updated database configuration details and added state caching settings.
docs/drupal/web/sites/development.services.yml Added comments on overriding container parameters for debugging purposes.
docs/drupal/web/sites/example.sites.php Updated URLs in comments for multi-site support.

Poem

🐇 In the world of Drupal's code,
Changes come, a fresh new load.
Configs tweaked, dependencies grown,
Fields and modules newly shown.
With bits of JSON and YAML's might,
Our Drupal site now shines so bright.
Hopping on to future's light,
A rabbit's work is never quite light. 🌟


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 0e8d98a and a21cb35.

Files ignored due to path filters (1)
  • docs/drupal/composer.lock is excluded by !**/*.lock
Files selected for processing (38)
  • docs/drupal/.ddev/docker-compose.env.yaml (1 hunks)
  • docs/drupal/composer.json (2 hunks)
  • docs/drupal/config/sync/block_content.type.banner_block.yml (1 hunks)
  • docs/drupal/config/sync/block_content.type.basic.yml (1 hunks)
  • docs/drupal/config/sync/block_content.type.disclaimer_block.yml (1 hunks)
  • docs/drupal/config/sync/block_content.type.footer_promo_block.yml (1 hunks)
  • docs/drupal/config/sync/core.extension.yml (1 hunks)
  • docs/drupal/config/sync/editor.editor.basic_html.yml (1 hunks)
  • docs/drupal/config/sync/editor.editor.full_html.yml (1 hunks)
  • docs/drupal/config/sync/jsonapi.settings.yml (1 hunks)
  • docs/drupal/config/sync/language/es/views.view.related_recipes.yml (2 hunks)
  • docs/drupal/config/sync/node.type.article.yml (1 hunks)
  • docs/drupal/config/sync/node.type.page.yml (1 hunks)
  • docs/drupal/config/sync/node.type.recipe.yml (1 hunks)
  • docs/drupal/config/sync/system.cron.yml (1 hunks)
  • docs/drupal/config/sync/system.date.yml (1 hunks)
  • docs/drupal/config/sync/system.site.yml (1 hunks)
  • docs/drupal/config/sync/taxonomy.vocabulary.recipe_category.yml (1 hunks)
  • docs/drupal/config/sync/taxonomy.vocabulary.tags.yml (1 hunks)
  • docs/drupal/config/sync/views.view.archive.yml (1 hunks)
  • docs/drupal/config/sync/views.view.block_content.yml (1 hunks)
  • docs/drupal/config/sync/views.view.content.yml (1 hunks)
  • docs/drupal/config/sync/views.view.featured_articles.yml (1 hunks)
  • docs/drupal/config/sync/views.view.files.yml (2 hunks)
  • docs/drupal/config/sync/views.view.glossary.yml (1 hunks)
  • docs/drupal/config/sync/views.view.media.yml (2 hunks)
  • docs/drupal/config/sync/views.view.media_library.yml (1 hunks)
  • docs/drupal/config/sync/views.view.moderated_content.yml (2 hunks)
  • docs/drupal/config/sync/views.view.recipes.yml (1 hunks)
  • docs/drupal/config/sync/views.view.related_recipes.yml (2 hunks)
  • docs/drupal/config/sync/views.view.taxonomy_term.yml (1 hunks)
  • docs/drupal/config/sync/views.view.user_admin_people.yml (1 hunks)
  • docs/drupal/config/sync/views.view.watchdog.yml (1 hunks)
  • docs/drupal/web/autoload.php (1 hunks)
  • docs/drupal/web/sites/default/default.services.yml (2 hunks)
  • docs/drupal/web/sites/default/default.settings.php (7 hunks)
  • docs/drupal/web/sites/development.services.yml (1 hunks)
  • docs/drupal/web/sites/example.sites.php (2 hunks)
Files skipped from review due to trivial changes (30)
  • docs/drupal/.ddev/docker-compose.env.yaml
  • docs/drupal/config/sync/block_content.type.basic.yml
  • docs/drupal/config/sync/block_content.type.disclaimer_block.yml
  • docs/drupal/config/sync/block_content.type.footer_promo_block.yml
  • docs/drupal/config/sync/core.extension.yml
  • docs/drupal/config/sync/editor.editor.basic_html.yml
  • docs/drupal/config/sync/editor.editor.full_html.yml
  • docs/drupal/config/sync/jsonapi.settings.yml
  • docs/drupal/config/sync/language/es/views.view.related_recipes.yml
  • docs/drupal/config/sync/node.type.article.yml
  • docs/drupal/config/sync/node.type.page.yml
  • docs/drupal/config/sync/node.type.recipe.yml
  • docs/drupal/config/sync/system.cron.yml
  • docs/drupal/config/sync/system.date.yml
  • docs/drupal/config/sync/system.site.yml
  • docs/drupal/config/sync/taxonomy.vocabulary.recipe_category.yml
  • docs/drupal/config/sync/taxonomy.vocabulary.tags.yml
  • docs/drupal/config/sync/views.view.archive.yml
  • docs/drupal/config/sync/views.view.block_content.yml
  • docs/drupal/config/sync/views.view.content.yml
  • docs/drupal/config/sync/views.view.featured_articles.yml
  • docs/drupal/config/sync/views.view.glossary.yml
  • docs/drupal/config/sync/views.view.media_library.yml
  • docs/drupal/config/sync/views.view.taxonomy_term.yml
  • docs/drupal/config/sync/views.view.user_admin_people.yml
  • docs/drupal/config/sync/views.view.watchdog.yml
  • docs/drupal/web/autoload.php
  • docs/drupal/web/sites/default/default.services.yml
  • docs/drupal/web/sites/development.services.yml
  • docs/drupal/web/sites/example.sites.php
Additional comments not posted (9)
docs/drupal/config/sync/block_content.type.banner_block.yml (1)

9-9: Approved change to revision management.

The change from 0 to false in the revision field likely indicates a shift from numeric to boolean management of revisions. This is a standard practice for simplifying configuration.

Please ensure that this change does not adversely affect any existing content where revisions were previously enabled.

docs/drupal/composer.json (2)

75-78: Highlight on patch documentation.

Documenting patches applied to modules like drupal/decoupled_router and drupal/jsonapi_menu_items is an excellent practice for traceability.

Ensure that these patches are re-evaluated with each new release of the related modules to confirm if they are still necessary or have been incorporated upstream.


21-28: Approved updates and additions to dependencies.

Updating Drupal core packages to 10.3.1 and adding modules such as drupal/jsonapi_menu_items and drupal/jsonapi_resources are crucial for maintaining up-to-date functionality.

Ensure comprehensive testing is conducted to verify that the new and updated packages integrate smoothly with the existing codebase.

Verification successful

Verified integration of new dependencies.

The new dependencies drupal/jsonapi_menu_items and drupal/jsonapi_resources are correctly integrated into the project as evidenced by their presence in the composer.json and composer.lock files, as well as multiple references throughout the codebase.

  • docs/drupal/composer.json
  • docs/drupal/composer.lock
  • docs/drupal/config/sync/core.extension.yml
  • docs/nuxt/content/guide/multilingual.md
  • docs/nuxt/content/modules/menu/README.md
  • examples/_deprecated/menu-edit/pages/index.vue
  • packages/menu/src/menu.js
  • packages/menu/src/typedefs/menuOptions.js
  • packages/menu/README.md
  • test/__fixtures__/get/*.json

Ensure comprehensive testing is conducted to verify that the new and updated packages integrate smoothly with the existing codebase.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify integration of new and updated packages.

# Test: Check for any integration issues in test logs or by running a composer update in a test environment.
echo "Run composer update and check test logs for integration issues."

Length of output: 136


Script:

#!/bin/bash
# Search for the new dependencies in the composer.json file
rg 'drupal/jsonapi_menu_items|drupal/jsonapi_resources' docs/drupal/composer.json

# Check for any references to these new dependencies in the codebase
rg 'jsonapi_menu_items|jsonapi_resources' src/

Length of output: 309


Script:

#!/bin/bash
# Locate potential source directories
fd --type d --max-depth 2

# Check for any references to these new dependencies in the located source directories
fd --type d --max-depth 2 | xargs -I {} rg 'jsonapi_menu_items|jsonapi_resources' {}

Length of output: 8023

docs/drupal/config/sync/views.view.recipes.yml (1)

95-95: Approved addition of pagination heading level.

Setting pagination_heading_level: h4 enhances accessibility by providing a proper semantic structure for pagination controls.

Verify that this change positively impacts the accessibility of the site, possibly by conducting an accessibility audit.

Verification successful

Approved addition of pagination heading level.

Setting pagination_heading_level: h4 enhances accessibility by providing a proper semantic structure for pagination controls. This change is consistent with the configuration across other views in the codebase.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the impact of the pagination heading level change on accessibility.

# Test: Conduct an accessibility audit to ensure the heading level change meets accessibility standards.
echo "Conduct an accessibility audit focusing on pagination controls."

Length of output: 136


Script:

#!/bin/bash
# Search for the usage of `pagination_heading_level` in the codebase to understand its impact.

# Find all occurrences of `pagination_heading_level` in the codebase
rg 'pagination_heading_level'

Length of output: 1277

docs/drupal/config/sync/views.view.related_recipes.yml (1)

Line range hint 159-190: Approved enhancements to filtering capabilities.

Updating the plugin_id to entity_target_id and adding target_entity_type_id: taxonomy_term under filters enhance the view's filtering capabilities, making it more specific and functional.

Verify that these changes function correctly and enhance the user experience as intended.

Verification successful

Changes verified in the configuration file.

The plugin_id is correctly set to entity_target_id, and target_entity_type_id is set to taxonomy_term in the views.view.related_recipes.yml file.

  • plugin_id: entity_target_id is present.
  • target_entity_type_id: taxonomy_term is present.

Recommend manually verifying the functionality of these filters to ensure they work as intended in the test environment.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the functionality of the updated filtering capabilities.

# Test: Check the view configuration in a test environment to ensure the filters are working as expected.
echo "Check the functionality of filters in a test environment."

Length of output: 124


Script:

#!/bin/bash
# Verify the presence and correctness of `plugin_id` and `target_entity_type_id` in the views.view.related_recipes.yml file.

# Search for `plugin_id` in the file
echo "Checking for plugin_id in views.view.related_recipes.yml:"
rg 'plugin_id: entity_target_id' docs/drupal/config/sync/views.view.related_recipes.yml

# Search for `target_entity_type_id` in the file
echo "Checking for target_entity_type_id in views.view.related_recipes.yml:"
rg 'target_entity_type_id: taxonomy_term' docs/drupal/config/sync/views.view.related_recipes.yml

Length of output: 547

docs/drupal/config/sync/views.view.moderated_content.yml (1)

438-438: Approved: Added pagination heading level for accessibility.

The addition of pagination_heading_level: h4 enhances accessibility and SEO by providing a proper HTML structure for pagination links.

docs/drupal/config/sync/views.view.media.yml (1)

137-137: Approved: Optimized image loading settings.

The settings for image_style as thumbnail and image_loading attribute set to lazy are excellent for optimizing performance by reducing initial page load times.

docs/drupal/config/sync/views.view.files.yml (1)

538-538: Approved: Added pagination heading level for better accessibility.

The addition of pagination_heading_level: h4 enhances accessibility and SEO by providing a proper HTML structure for pagination links.

docs/drupal/web/sites/default/default.settings.php (1)

80-80: Update to database configuration details.

The database name in the MySQL configuration example has been updated to database_name. This change should be reflected in any documentation and scripts that reference the old database name.

Copy link

codecov bot commented Jul 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.19%. Comparing base (0e8d98a) to head (a21cb35).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #694   +/-   ##
========================================
  Coverage    96.19%   96.19%           
========================================
  Files           91       91           
  Lines         2367     2367           
  Branches       511      511           
========================================
  Hits          2277     2277           
  Misses          75       75           
  Partials        15       15           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant