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
As discussed lately, we need to investigate a way to ensure parse() always returns "something". This could be processing page contents a little like how node-unfluff does, as a last-resort fallback strategy.
The text was updated successfully, but these errors were encountered:
While reading the code flow today, I've noticed that relaxing the number of chars considered not enough for generated page contents to be acceptable[0] helps avoiding having null returned as a result.
As discussed lately, we need to investigate a way to ensure
parse()
always returns "something". This could be processing page contents a little like how node-unfluff does, as a last-resort fallback strategy.The text was updated successfully, but these errors were encountered: