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

auto generate entrypoint for block.json files #132

Closed
wants to merge 11 commits into from

Conversation

fabiankaegy
Copy link
Member

Description of the Change

This is currently broken!!!

Closes #130

Alternate Designs

Possible Drawbacks

Verification Process

Checklist:

  • I have read the CONTRIBUTING document.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my change.
  • All new and existing tests passed.

Changelog Entry

Credits

Props @

@github-actions
Copy link
Contributor

ESLint Summary View Full Report

Annotations are provided inline on the Files Changed tab. You can also see all annotations that were generated on the annotations page.

Type Occurrences Fixable
Errors 0 0
Warnings 1 0
Ignored 0 N/A
  • Result: ✅ success

  • Annotations: 1 total


[warning] jsdoc/check-indentation

Reports invalid padding inside JSDoc blocks.


Report generated by eslint-plus-action

nicholasio and others added 2 commits March 3, 2022 00:33
…o-include-blocks

# Conflicts:
#	package-lock.json
#	projects/10up-theme/includes/blocks/example-block/block.json
@fabiankaegy
Copy link
Member Author

Closing this in favor of #195

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.

Scan block.json files to auto detect entry points for the build process
2 participants