Today, Phlow outputs all errors by simply printing numerous error enums scattered throughout the code. While this works to some extent, it is far from elegant.
The proposal is:
Improve the display of runtime, step, and PHS errors by following a unified visual standard.
Create an analyzer capable of generating suggestions for fixing common errors. (Maybe a future dream?)
Today, Phlow outputs all errors by simply printing numerous error enums scattered throughout the code. While this works to some extent, it is far from elegant.
The proposal is:
Improve the display of runtime, step, and PHS errors by following a unified visual standard.
Create an analyzer capable of generating suggestions for fixing common errors. (Maybe a future dream?)