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

Fix block assets compilation #1122

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Fix block assets compilation #1122

wants to merge 5 commits into from

Conversation

asharirfan
Copy link
Contributor

Description

This PR introduces the following changes in wd_s:

  • Fix block scaffolding command
  • Fix block.json template
  • Fix block style files
  • Fix block assets compilation
  • Move blocks register function to a more appropriate location

What type of PR is this? (put an x to all applicable)

  • πŸ• Feature
  • πŸ› Bug Fix
  • πŸ“ Documentation Update
  • 🎨 Style
  • πŸ§‘β€πŸ’» Code Refactor
  • πŸ”₯ Performance Improvements
  • βœ… Test
  • πŸ€– Build
  • πŸ” CI
  • πŸ“¦ Chore (Release)
  • ⏩ Revert

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

  • πŸ‘ yes
  • πŸ™… no, because they aren't needed
  • πŸ™‹ no, because I need help

Added to documentation?

  • πŸ“œ README.md
  • πŸ““ Confluence
  • πŸ™… no documentation needed

Reviewer's Testing Checklist

As a reviewer, please ensure the following testing criteria are met and validated before approving this Pull Request.

  • Visual Regression Testing: Ensure that existing functionality is not negatively impacted by the changes.
  • Cross-Browser Compatibility: Test on major browsers (Chrome, Firefox, Safari) to ensure compatibility.
  • Mobile Responsiveness: Confirm that the changes are responsive and functional on various mobile devices.
  • Accessibility Testing: Validate that the changes comply with accessibility standards.
  • Linting: Check that the code passes all linting checks (PHPCS, ESLint, SassLint).
  • Theme Compatibility: Ensure that the changes do not adversely affect the site's theme and styling.
  • Plugin Compatibility: Check if the changes are compatible with existing plugins and do not cause conflicts.
  • Core Functionality: Verify that the WordPress core functionalities are not disrupted.
  • Custom Post Types and Taxonomies: Confirm that any custom post types or taxonomies function as intended.
  • Security Best Practices: Ensure that the code follows WordPress security best practices.
  • Performance: Check for any performance issues, especially with database queries and page load times.
  • SEO Considerations: Where applicable, confirm that the changes do not negatively impact SEO elements.
  • WordPress Coding Standards: Ensure that the code adheres to WordPress coding standards.
  • Documentation: Ensure that any new features or changes are appropriately documented in the README.md or Confluence.
  • User Acceptance Testing (UAT): If applicable, confirm that stakeholders have reviewed and accepted the changes.
  • Post-Deployment Tasks: Check if there are any tasks that need to be performed after deployment.

[optional] Additional Reviewer Notes or Considerations?

@asharirfan asharirfan self-assigned this Feb 23, 2024
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.

None yet

1 participant