We default to 800 which had been fine and good...pre Gutes.
Due to how blocks were made and the delimiters for each block, we're going to hit the limit pretty quick.
Do we want to simply increase that limit a lot for WP 5.0.0+ ? We have a filter available already that we could conditionally use.
Do we want to investigate the regex that core may use to parse out each block, and re-use that ourselves to strip the delimiters out before we do our own string searching?
Do we want to just do preg_match_all on the entirety of the content string and do away with the limit completely? We'd be able to pluck out the first found result anyway.
We default to 800 which had been fine and good...pre Gutes.
Due to how blocks were made and the delimiters for each block, we're going to hit the limit pretty quick.
Do we want to simply increase that limit a lot for WP 5.0.0+ ? We have a filter available already that we could conditionally use.
Do we want to investigate the regex that core may use to parse out each block, and re-use that ourselves to strip the delimiters out before we do our own string searching?
Do we want to just do preg_match_all on the entirety of the content string and do away with the limit completely? We'd be able to pluck out the first found result anyway.