Skip to content
This repository has been archived by the owner on Feb 24, 2023. It is now read-only.

break change of settings.json #20

Open
CoffeeChaton opened this issue Feb 4, 2023 · 1 comment
Open

break change of settings.json #20

CoffeeChaton opened this issue Feb 4, 2023 · 1 comment

Comments

@CoffeeChaton
Copy link
Owner

CoffeeChaton commented Feb 4, 2023

I plan to rename some settings to be closer to the naming style of vsc.
I would like to investigate a better/more specific naming and description

// settings.json

     // old "AhkNekoHelp.baseScan.IgnoredList": 
    "AhkNekoHelp.files.WorkspacesExclude": [
        "/\\.", // Any folder/file starting with "." contains .git, .vscode, etc.
        "/node_modules$", // file-path Include node_modules
        "/node_modules/", // file-path Include node_modules
        // some demo
        "/neko_Exp_Gdip\\.ahk$",
        "/build(/|$)",
        "/dist(/|$)",
        "/temp(/|$)",
        "/ahk2(/|$)", // file-path Include /ahk2/   exp:  `D:/dev/ahk2/`
        "\\.2\\.ahk$" // file-path Include .2.ahk    exp:  `D:/dev/demo.2.ahk`
    ],
    // old "AhkNekoHelp.snippets.blockFilesList":
    "AhkNekoHelp.files.CompletionExclude": [
        "/Gdip_all_2020_08_24\\.ahk"
    ]

AhkNekoHelp.files.WorkspacesExclude

  1. workspace scan blockList, Disable AhkNekoHelp when the file path contains a match of any of the provided Array of RegExp. \n\nNote: pathname separator use \"/\" not windows-style \"\\\"
  2. ...not any idea

AhkNekoHelp.files.CompletionExclude

  1. Disable IntelliSense when the file path contains a match of any of the provided Array of RegExp. \n\nNote: pathname separator use \"/\" not windows-style \"\\\"
  2. ...not any idea
@CoffeeChaton
Copy link
Owner Author

AhkNekoHelp.files.WorkspacesExclude

  1. workspace pack index make blockList, Disable AhkNekoHelp make index of the file path contains a match of any of the provided Array of RegExp.
    > Note: path name separator use "/" not windows-style "\".
    > this is to avoid multiple escaping semantics when writing rules.
  2. In projects where you have both old and new versions of a file and have functions with the same name defined in different files, it is recommended to use this option and write rules to avoid a series of malfunctions such as jumps, Read More

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant