Pieter Van der Haegen
Pieter Van der Haegen
Also having the same issue but not using `setFieldError` only `setFieldValue` & `setFieldTouched`. It's indeed related to https://github.com/formium/formik/pull/3201. When I log all the errors I think this conditional was actually...
@evcodes the issue is still present. Could you re-open please?
@rsese thanks for the elaborated report! Is this a bug in tree-sitter then or not? Should I file it there?
When I opened my Computer after the weekend all colors looked right... I have no clue why but the issue is solved for now!
Sorry My theme was not saved... the issue is still persistent
Is there any progress on this? It would be very awesome!
I get the point but in this specific use case we would define a constant for all CSS values that are strings and create them in every file or create...
I think you finally found the first Micro user to need this 😛 We're a very small development team though so not sure if we have bandwidth to do this....
@salvadortorrubiaNexplore that's not really a good solution IMO This warning is driving me crazy and polluting our test output with thousands of rows... (the whole document node get's printed). @benjamn...
@theBrianCui that's already a more elegant solution, but still not great IMO @benjamn any input how this can be solved better? I'm open to contributing but would like some direction...