PLW-07203, any way to control the PLSQL_WARNINGS values specified by Raptor

Question

While debugging some packaged code and compiling the specification through Raptor, I got the PLW_07203 warning, which was deemed to be an error and therefore prevented me from compiling the code successfully in Raptor.
First, is it correct for Raptor to consider these types of compilation warnings to be errors?
Second, since Raptor sets the PLSQL_WARNINGS parameter for the session, is there any way to control that parameter setting? For now, it seems to always specify it by executing ALTER SESSION SET PLSQL_WARNINGS = 'ENABLE:ALL'.
Third, is it possible for Raptor to tell that I've loaded the source for a package specification or body from the data dictionary and have made no changes to it before I ask it to be compiled? Now, it seems that Raptor always is recompiling the package code by using the CREATE OR REPLACE construct, so it will overwrite any existing PLSQL object settings that may have been defined for the code previously. If you could detect that I'm simply asking you to recompile the source (primarily to simply get it compiled with debug information), then you could use the ALTER PACKAGE syntax for the recompilation. That with the ability to specify whether or not the REUSE SETTINGS clause would allow people to compile packages without getting into problems from Raptor changing the PLSQL_WARNINGS session parameter.

Answer 1

1) It's already bugged.
2) This is planned for production
3) There's a right click compile from dictionary which just does an alter ... compile. The new drop coming this week will change how browsing code works so that there's a read-only copy with an edit button to launch the editor.
-kris