Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

WordPress / gutenberg Public

Notifications You must be signed in to change notification settings
Fork 4.3k
Star 10.7k

Code
Issues 5k+
Pull requests 1.5k
Discussions
Actions
Projects 8
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Don't try to parse strings that don't contain blocks#3903

Merged

youknowriad merged 4 commits intomasterWordPress/gutenberg:masterfrom fix/3799-parse-oomWordPress/gutenberg:fix/3799-parse-oomCopy head branch name to clipboard

Dec 11, 2017

+15-1

Conversation Commits4 (4)Checks Files changed

Commits

Commits on Dec 11, 2017

Short circuit gutenberg_parse_blocks() calls when there are no blocks to parse
pento
committed
Fix linting errors.
pento
committed
Add checks for  and 
pento
committed
Use gutenberg_content_has_blocks to check for existance of blocks
youknowriad
committed

Footer

© 2024 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.