Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-31813

Code Block - Language: PowerShell - Refined code highlighting

XMLWordPrintable

    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      I'd love to have some refinements to the codeblock parsing of the supported PowerShell highlighter:

      • Everything between '<#' and '#>' (not counting the single hyphens) is a comment. even - or rather especially - if it spans multiple lines.
      • If behind the command "New-Object" is a string with dots inbetween (like ABC.DEF.GHI), that's a .NET class. Special highlighting for that might be appropriate.
      • [ABC.DEF.GHI] is another .NET specific notation
      • [ABC.DEF.GHI]::Function() is calling a .NET function (or property, if called without the "()"). Highlighting those function or property-stubs separately would be great
      • Functions and their parameters appear to be colored in the same color ("Select-Object -First"). I'd much appreciate if those could be varied, so that functions and parameters have similar colors (Example: Functions get a dark blue and parameters a light blue). Powershell code frequently consists of long chains of Function Pipelines with little but functions and their parameters.
      • There is a way in powershell to create a string object across multiple lines: They start with '@"' and end with '"@' (without the single hyphens, but with the double ones). This is not supported in the PowerShell highlighter so far.

      All those would be nice-to-have, though hardly worldshaking, features

            [CONFSERVER-31813] Code Block - Language: PowerShell - Refined code highlighting

            Sen made changes -
            Workflow Original: JAC Suggestion Workflow 4 [ 3579629 ] New: JAC Suggestion Workflow 3 [ 4337639 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow 2 [ 3185749 ] New: JAC Suggestion Workflow 4 [ 3579629 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3037157 ] New: JAC Suggestion Workflow 2 [ 3185749 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2530092 ] New: JAC Suggestion Workflow [ 3037157 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 2260203 ] New: Confluence Workflow - Public Facing v4 [ 2530092 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 - TEMP [ 2197753 ] New: Confluence Workflow - Public Facing v3 [ 2260203 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v3 [ 1938892 ] New: Confluence Workflow - Public Facing v3 - TEMP [ 2197753 ]
            Katherine Yabut made changes -
            Workflow Original: Confluence Workflow - Public Facing v2 [ 1756935 ] New: Confluence Workflow - Public Facing v3 [ 1938892 ]
            jonah (Inactive) made changes -
            Description Original: I'd love to have some refinements to the codeblock parsing of the supported PowerShell highlighter:
            - Everything between '<#' and '#>' (not counting the single hyphens) is a comment. even - or rather especially - if it spans multiple lines.
            - If behind the command "New-Object" is a string with dots inbetween (like ABC.DEF.GHI), that's a .NET class. Special highlighting for that might be appropriate.
            - [ABC.DEF.GHI] is another .NET specific notation
            - [ABC.DEF.GHI]::Function() is calling a .NET function (or property, if called without the "()"). Highlighting those function or property-stubs separately would be great
            - Functions and their parameters appear to be colored in the same color ("Select-Object -First"). I'd much appreciate if those could be varied, so that functions and parameters have similar colors (Example: Functions get a dark blue and parameters a light blue). Powershell code frequently consists of long chains of Function Pipelines with little but functions and their parameters.
            - There is a way in powershell to create a string object across multiple lines: They start with '@"' and end with '"@' (without the single hyphens, but with the double ones). This is not supported in the PowerShell highlighter so far.

            All those would be nice-to-have, though hardly worldshaking, features :)             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *Confluence Server*. Using *Confluence Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/CONFCLOUD-31813].
              {panel}

            I'd love to have some refinements to the codeblock parsing of the supported PowerShell highlighter:
            - Everything between '<#' and '#>' (not counting the single hyphens) is a comment. even - or rather especially - if it spans multiple lines.
            - If behind the command "New-Object" is a string with dots inbetween (like ABC.DEF.GHI), that's a .NET class. Special highlighting for that might be appropriate.
            - [ABC.DEF.GHI] is another .NET specific notation
            - [ABC.DEF.GHI]::Function() is calling a .NET function (or property, if called without the "()"). Highlighting those function or property-stubs separately would be great
            - Functions and their parameters appear to be colored in the same color ("Select-Object -First"). I'd much appreciate if those could be varied, so that functions and parameters have similar colors (Example: Functions get a dark blue and parameters a light blue). Powershell code frequently consists of long chains of Function Pipelines with little but functions and their parameters.
            - There is a way in powershell to create a string object across multiple lines: They start with '@"' and end with '"@' (without the single hyphens, but with the double ones). This is not supported in the PowerShell highlighter so far.

            All those would be nice-to-have, though hardly worldshaking, features :)
            jonah (Inactive) made changes -
            Link New: This issue relates to CONFCLOUD-31813 [ CONFCLOUD-31813 ]

              smansour Sherif Mansour
              350037d2b12c Friedrich Weinmann
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: