As I’ve used the Fuel tech stack more and more, I’ve feel like I’ve made steps to make the following process faster and faster:
- Make code change
- Compile code
- Identify error to target
There is an issue that developers will face if they try to compile everything (i.e. multiple modules) at once.
If there is a module dependency which fails to compile, the compiler will act as if that type doesn’t exist from that module.
Then every use of that type will print an error to the console.
1 simple error in a dependency file can result in 100s of downstream errors for files that rely on an upstream dependency.
Even within the same file it will still the remaining even though a dependency has errors within it, flagging it as type "{unknown}".
I’m having trouble reproducing the exact scenario where there are cascading errors that really pile up.
If anyone has encountered something similar or can reproduce the exact scenario of cascading errors, please feel free to comment below.
Excited to be apart of the Fuel dev community and thanks to the Fuel Labs team for all their support.
- alphak3y
) , Just for missing something small like END IF or a semi-colon.