If you like the idea (or at least agree with the motive behind it) please vote for it.Įnhancement / Logger / oracle-sql-developer / “Gold-plated” Option: add an option to the SQL Editor’s right-click context menu – on any identifier, select “Hide all lines with reference to this” and it adds the identifier to the list of things that are hidden! Mockup #2 (identifier slugs in header bar to show/hide, with icons in the gutter showing where lines have been hidden): Mockup #1 (alternative syntax highlighting option): “logger”, “logger_logs”) any PL/SQL declarations or lines of code containing references to these objects would be greyed out, or be able to be rolled up (with something like the +/- gutter buttons).” “One way I expect this might work is that the Code Editor would be given a configurable list of oracle object identifiers (e.g. grey highlight) any code calling their preferred debug/instrumentation library (e.g. “The oracle open source Logger instrumentation library is gaining popularity and it would be great to build some specific support for it into SQL Developer, whether as a plugin or builtin. To enhance code readability, it would be helpful for PL/SQL developers to be able to hide/show, or dim (e.g. Logger: show/hide or dim (highlight) debug/instrumentation code Therefore, I have raised the following enhancement request at the SQL Developer Exchange: However, the readability of code is still an issue so it was with that in mind that I suggested that perhaps an enhancement of our favourite development IDE would go a long way to improving the situation. In the judgement of some (myself included) the addition of the synonym to the standard package would run the risk of causing clashes on some people’s systems and ensuring that Logger is installable on all systems “out of the box” should, I think, take precedence. The motive behind this request was to allow our PL/SQL code to remain easy to read, in spite of all the calls to logger sprinkled throughout that are needed for effective debugging and instrumentation. Juergen Schuster, who has been enthusiastically trying OraOpenSource Logger, raised an idea for the debug/instrumentation library requesting the addition of a standard synonym “l” for the package. UPDATE – new feature added in Oracle SQL Developer 18.3 I haven’t worked out how to include these in the rule yet.Įnhancement Request for SQL Developer for users of Logger The only thing missing is that it doesn’t pick up the standard logger variable declarations (scope and params). I’m not very familiar with the syntax but you can add additional libraries by adding more lines like this to the rule: You can view (and edit, if you want) the rule in PL/SQL Custom Syntax Rules: You can customise the colour for this rule in Tools -> Preferences -> Code Editor -> PL/SQL Syntax Colors – the one for logger etc. Any calls to logger, dbms_output and apex_debug will be greyed out. Oracle SQL Developer 18.3 adds this feature with PL/SQL Custom Syntax Rules – and the best thing is, these rules are enabled by default so you don’t have to do anything. Custom Syntax Highlighting in SQL DeveloperĪ few years ago I raised an enhancement request for SQL Developer to add custom highlighting, specifically to “grey out” all the calls to logger throughout my code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |