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
I'm not sure we are going to change this for v2 anymore, because in v3 we use static analysis to generate the bindings.
Nevertheless you can use the build tag bindings to detect if the app is being built for binding generation or not. So if the bindings tag is used, you can conditionally skip the setup of the panic.log error handler and you should be fine.
Description
When I redirect error output to file on Windows, I found a lot of output from wails.
I checked the wails source code and found output here is
println
:But
println
wtrites the result to standard errorTo Reproduce
file
internal\typescriptify\typescriptify.go
line659, 660
Expected behaviour
Write to standard output
Screenshots
No response
Attempted Fixes
This shuould be write to std output. such as
fmt.println
System Details
Additional context
No response
The text was updated successfully, but these errors were encountered: