[转帖]Code brushes for GitHub Copilot

code,brushes,for,github,copilot · 浏览次数 : 0

小编点评

## Code Brushes for GitHub Copilot The article provides an introduction to code brushes for GitHub Copilot labs and how they can help improve the quality of your code. **Key takeaways:** * **Code cleaner:** The new feature allows you to change code to make it cleaner, more robust, and document it automatically. * **Improved code:** Using brushes like "Fix bugs," "Clean," "List steps," and "Make robust," you can improve the quality of your code by catching errors and adding comments. * **Custom brushes:** You can define custom brushes to achieve specific code formatting or quality checks. * **Benefits:** This feature can significantly improve the quality and maintainability of your code. **Additional points:** * The article mentions the "Add types" brush, but it's not mentioned in the main text. * The article focuses on JavaScript code, but the functionality can be applied to other programming languages. **Overall, the article provides a good overview of the new code brushes feature and how they can help improve your code's quality.**

正文

https://christianheilmann.com/2022/12/13/code-brushes-for-github-copilot/

Tuesday, December 13th, 2022 at 4:45 pm

Github Next now showed a new feature in GitHub Copilot labs that allows you to change code you write to make it cleaner, more robust and document it automatically.

GitHub Copilot is incredible, and if you check what’s happening in the preview released as the Copilot Labs extension it will only get more amazing.

Check this out:

Code brushes applied to a simple JavaScript

Let’s start with a basic JavaScript that checks a string length and reports when it is empty. One with an obvious mistake, as we use a single `=` instead of the type safe `===`. This will always report the string as empty.

if (str.length = 0) {
    console.error('String is empty');
}

Using the `Fix bugs` brush, this is rectified.

if (str.length === 0) {
    console.error('String is empty');
}

Using the `Clean` brush also adds reporting when the string is not empty.

if (str.length === 0) {
    console.error('String is empty');
} else {
    console.log('String is not empty');
}

Using the `List steps` brush adds comments for step (sure, this is redundant, but it also works for much more complex code).

// check the length of the string
if (str.length === 0) {
    // if length is 0, print 'String is empty' 
    console.error('String is empty');
} else {
    // if length is not 0, print 'String is not empty'
    console.log('String is not empty');
}

Using `Make robust` adds error reporting instead of logging and an extra check to make sure that `str` is really a String and not an empty Array.

function test(str) {
    if (str.length === 0) {
        throw new Error('String is empty');
    } else if (typeof str !== 'string') {
        throw new Error('It is not a string');
    } else {
        console.log('String is not empty');
    }
}

The `Add types` brush does exactly that.

/**
 * @param {string} str
 * @returns {string}
 */
function test(str) {
    if (str.length === 0) {
        throw new Error('String is empty');
    } else if (typeof str !== 'string') {
        throw new Error('It is not a string');
    } else {
        console.log('String is not empty');
    }
}

You can also define custom brushes and there are more to come.

Share on Twitter