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 mentioned in the docs, console.assert prints the error to stderr, but it does not throw an error. It means the script still exits with exit code 0 (if everything goes well).
Showing "Assertion error" and also showing "Example ran successfully" makes no sense. So, we should remove "Example ran successfully" message from the examples in Fae. It will result in cleaner example scripts in Fae and more reliable failing chec in Fae.
But in the playground, it will not be apparent when the script ran successfully because there will no output in case of examples. Not only in case of examples, some developer will write a code for type check in the playground, or use console.assert in their script. So it is more advisable to show successful notification/popup in the playground.
The text was updated successfully, but these errors were encountered:
#33 (comment)
Showing "Assertion error" and also showing "Example ran successfully" makes no sense. So, we should remove "Example ran successfully" message from the examples in Fae. It will result in cleaner example scripts in Fae and more reliable failing chec in Fae.
But in the playground, it will not be apparent when the script ran successfully because there will no output in case of examples. Not only in case of examples, some developer will write a code for type check in the playground, or use
console.assert
in their script. So it is more advisable to show successful notification/popup in the playground.The text was updated successfully, but these errors were encountered: