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

Bug: Latest update means a blank fields field causes an error #265

Closed
SkepticMystic opened this issue Jan 11, 2022 · 0 comments
Closed

Bug: Latest update means a blank fields field causes an error #265

SkepticMystic opened this issue Jan 11, 2022 · 0 comments
Labels
bug Something isn't working view:codeblock:tree

Comments

@SkepticMystic
Copy link
Owner

SkepticMystic commented Jan 11, 2022

It's this code here.
First check if(f !== undefined ....
Making it a flat array means forEach always runs, even if fields coming in from the parsedSource is undefined.

[fields].flat()?.forEach((f) => {

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working view:codeblock:tree
Projects
None yet
Development

No branches or pull requests

1 participant