The code that is generated by the code editor should be run through the compiler to check for compiler warnings, and when compiler warnings occur, they should be flagged on the relevant block, with a link to a documentation page that explains the error and what to do about it.
If it is not feasible to relate compiler warnings back to the block that created them, some subset of the possible warnings should be implemented as a code validation that generates the same interface. A warning icon similar to the question mark used for comments would be a good first attempt for a warning interface.
There are likely Blockly library features to facilitate this sort of thing.
The code that is generated by the code editor should be run through the compiler to check for compiler warnings, and when compiler warnings occur, they should be flagged on the relevant block, with a link to a documentation page that explains the error and what to do about it.
If it is not feasible to relate compiler warnings back to the block that created them, some subset of the possible warnings should be implemented as a code validation that generates the same interface. A warning icon similar to the question mark used for comments would be a good first attempt for a warning interface.
There are likely Blockly library features to facilitate this sort of thing.