JSONC | JSON compressor and decompressor | Compression library

You need to add "compat" like this

You can set a file association between json files and jsonc language formatting.

In VS Code open Settings in JSON view by using the Command Pallet (Cmd + Shift + P) and enter Preferences: Open Settings (JSON). Next, add the following (or append to the existing files.associations object if it already exists):

You are going to run into issues with this setup. See these related GitHub issues 1, 2.

Instead, use Deno's LSP in one workspace (your backend) and the vanilla TS LSP in the other workspace (your frontend), using exclusive VS Code settings files in each. (If you do repo top-level scripting with Deno, then it's fine to duplicate that VS Code config for the top-level, too.)

Then, open a separate VS Code window for each workspace in your monorepo so that they can use their own LSPs without conflict.

The problem was solved installing the PHP RPM files ignoring the dependencies from HTTPD and then moving the mod_php files (mod_php.so) from the original source directory into the respective modules directory from the HTTPD installed by source.

Your question lack some clarity for me as it stand.

Based on your post, what I understand is:

• You want to iterate through a list of folder $topMgFolderPath being the root folder.
• You used -Recurse in your code sample so I assumed you want to go all the way down the tree
• Based on your second code line ending of | should -BeNullOrEmpty, you are looking to trigger a Pester test failure if there is anything that do not correspond to your condition.
• You expect folders to have either a rbac.json file, in which case all the subfolders in that folder will be ignored from any further processing or at least 1 subfolder that will itself contains either a rbac.json file or more subfolders that will lead down the line to such a file.
• In all cases, .policy folder is to be ignored

Please update your question with additional details or clarify the situation if I didn't get the premise right.

In any case, what you seek to do is possible but not through a single Get-ChildItem statement.

The way I'd go about it, since you want a recurse operation with multiple checks that stop processing a folder once it has been validated, is an home-made -recurse done through a single-layer Get-ChildItem alongside a queue where the recursion is done "manually", one layer at a time within a while loop that persist until the queue is cleared out.

Update: Version v1.60.0 had a bug. Upgrade to v1.60.1 or higher for a fix.

The bug manifested in the following symptoms:

• The Open in Integrated Terminal shortcut-menu command in the Explorer pane's shortcut always uses the built-in default shell (PowerShell on Windows), ignoring the configured one.

• The same goes for running tasks (with or without a separate terminal.integrated.automationShell.* setting).

• Also, if a given folder or workspace happened to have an integrated terminal open when quitting Visual Studio Code, the shell that is launched when the integrated terminal automatically reopens the next time is again the built-in default shell, not the configured one. By contrast, if reopening doesn't auto-open the integrated terminal, opening it manually does respect the configured default shell, and so does manually creating another shell instance later.

See GitHub issue #132150

The following information turned out to be unrelated to the bug, but is hopefully still useful general information about Visual Studio Code's recent change in how shells for the integrated terminal are configured:

• Recently, the "terminal.integrated.shell.*" and "terminal.integrated.shellArgs.*" settings were deprecated and replaced with a more flexible model that allows defining multiple shells to select from, via so-called shell profiles, optionally defined in setting "terminal.integrated.profiles.*", with an associated mandatory "terminal.integrated.defaultProfile.*" setting referencing the name of the profile to use by default - which may be an explicitly defined custom profile or one of the built-in, platform-appropriate default profiles.

  • Note: * in the setting names above represents the appropriate platform identifier, namely windows, linux, or osx (macOS).

• As of v1.60.1, if legacy "terminal.integrated.shell.*" settings are also present, the new settings take precedence (even though the tooltip when editing "terminal.integrated.shell.*" in settings.json suggests that this change is yet to come).

  • In the absence of both settings, Visual Studio Code's built-in default shell is used, which on Windows is PowerShell,^[1] and on Unix-like platforms the user's default shell, as specified in the SHELL environment variable.

  • Recent Visual Studio Code versions, starting before v1.60 - seemingly as one-time opportunity - displayed a prompt offering to migrate the deprecated settings to the new ones.

    • Accepting the migration results in the following:

      • Creation of setting "terminal.integrated.shell.*" containing a custom shell profile derived from the values of legacy settings "terminal.integrated.shell.*" and, if present, "terminal.integrated.shellArgs.*"; that custom profile's name has the suffix (migrated)
      • Creation of setting terminal.integrated.defaultProfile.* whose value is the migrated profile's name, making it the default shell.
      • Removal of legacy settings "terminal.integrated.shell.*" and "terminal.integrated.shellArgs.*"

    • If you decline the migration, you can later effectively perform it by re-choosing the default shell, as described below.

      • Note: The new "terminal.integrated.defaultProfile.*" setting that is created in the process then effectively overrides the legacy "terminal.integrated.shell.*" and "terminal.integrated.shellArgs.*" settings, but the latter won't be removed automatically. To avoid confusion, it's best to remove them from settings.json manually.

• Choose the default shell profile to use in order to (re)specify the default shell:

  • Click on the down-arrow part of the shell-selector icon () on the right side of the integrated terminal, select Select Default Profile, which presents a list of the defined profiles to select the default from - in the absence of explicitly defined profiles, standard profiles are offered (see below).

  • This translates into a terminal.integrated.defaultProfile.* setting in settings.json, whose value is the name of the chosen shell profile - which may be the name of a built-in profile or one of the ones explicitly defined in "terminal.integrated.profiles.*"

  • Note: This shell is by default also used for tasks (defined in tasks.json), but that can be overridden with a "terminal.integrated.automationShell.*" setting pointing to the executable of an alternative shell.

• Optionally, in your settings.json file, you may create a platform-appropriate terminal.integrated.profiles.* setting with shell profiles of interest:

  • Note: Even if your settings.json contains no (platform-appropriate) "terminal.integrated.profiles.*" setting, Visual Studio code has built-in standard profiles it knows of and offers them for selection when choosing the default shell.

    • These standard profiles are a mix of shells that come with the host platform as well as some that Visual Studio detects dynamically on a given system, such as Git Bash on Windows.

  • To create the standard profiles explicitly, do the following:

    • Note: You may choose to do this in order to customize the standard profiles. However, if your intent is merely to add custom profiles - see this answer for an example - it isn't necessary to create the standard profiles inside the "terminal.integrated.profiles.*" setting, because Visual Studio Code knows about them even if not explicitly defined.

    • Via File > Preferences > Settings (Ctrl-,), search for profiles and click on Edit in settings.json below the platform-appropriate Terminal > Integrated > Profiles > * setting; this will open settings.json for editing, with the standard profiles added; simply saving the file is sufficient.

      • Note: If the "terminal.integrated.profiles.*" setting shown doesn't contain the expected, platform-appropriate standard profiles, a setting by that name may already be present; to force creation of the standard profiles, remove or comment out the existing setting and save the file, then try again.

    • On Windows, you'll end up with something like the following:

The error is a side effect of installing node-sass (i.e., selecting CSS Pre-processors, and Sass/SCSS (with node-sass)) without Python installed. node-sass's postinstall uses node-gyp, which requires Python, so if you don't have the python binary available in the environment path, the postinstall fails.

node-sass is not part of the default preset, so you wouldn't see the error installing the default.

Install Python. The package installers usually add the python binary to the environment path. Make sure to restart any open terminals to pick up the updated environment.

Use Vue CLI 5.x, which replaces node-sass (deprecated) with sass.

You can upgrade to 5.0.0-beta.3 (tagged next) with:

Your vs code is apparently using a more recent version of typescript than your package.json has, and as a result it's using a new option that the error in catch blocks be treated as unknown instead of any. To fix this, look at the bottom right of your vs code window and you should see the typescript version, something like this:

Click the version number and a dropdown will appear at the top of the screen

Click "Select Typescript Version" to change it.

Usually, vs code is able to figure out your workspace's version and will list that as a possibility. If for some reason it can't, or if you want to use a different version, you can tell typescript what to do with the "typescript.tsdk" setting. For information on how to set that up, see this page: https://code.visualstudio.com/docs/typescript/typescript-compiling#_using-the-workspace-version-of-typescript

install the extension PHP Extension Pack and PHP IntelliSense, also if you like to check for bug you will need to set you path to your php.exe in your setting.json example