Skip to content

Generates vscode settings with python paths for extensions#32

Merged
Mayankm96 merged 4 commits into
mainfrom
fix/vscode-settings
Mar 4, 2023
Merged

Generates vscode settings with python paths for extensions#32
Mayankm96 merged 4 commits into
mainfrom
fix/vscode-settings

Conversation

@Mayankm96
Copy link
Copy Markdown
Contributor

@Mayankm96 Mayankm96 commented Mar 4, 2023

Description

This PR adds generation of the VSCode .vscode/settings.json file from a template file in the .vscode/tools/settings.template.json.

The generation script fills the "python.analysis.extraPaths" attribute with the paths of the extensions in the Isaac Sim VSCode settings (_isaac_sim/.vscode/settings.json). This is necessary since some extensions are not being maintained in the setup_python_env.sh script. The script was earlier used to generate the .python.env file that listed the environment variables for the VSCode workspace.

The settings generation script runs automatically when the user runs:

./orbit.sh --install  # or `orbit.sh -i`

OR

./orbit.sh --vscode  # or `orbit.sh -v`

The main .vscode/settings.json file is now part of .gitignore and is excluded by default. Users must not modify this file directly.

Type of change

  • New feature (non-breaking change which adds functionality)
  • This change requires a documentation update

Checklist

  • I have run the pre-commit checks with ./orbit.sh --format
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • I have updated the changelog and the corresponding version in the extension's config/extension.toml file

@Mayankm96 Mayankm96 changed the title Adds generation of VS Code settings with extra python paths Generate VS Code settings with python paths for extensions Mar 4, 2023
@Mayankm96 Mayankm96 changed the title Generate VS Code settings with python paths for extensions Generates VS Code settings with python paths for extensions Mar 4, 2023
@Mayankm96 Mayankm96 changed the title Generates VS Code settings with python paths for extensions Generates vscode settings with python paths for extensions Mar 4, 2023
@Mayankm96 Mayankm96 merged commit ed94e76 into main Mar 4, 2023
@Mayankm96 Mayankm96 deleted the fix/vscode-settings branch March 4, 2023 21:43
@Mayankm96 Mayankm96 added the enhancement New feature or request label Mar 4, 2023
@Mayankm96 Mayankm96 self-assigned this Mar 4, 2023
Mayankm96 added a commit that referenced this pull request Jun 30, 2023
…ent variables (#33)

# Description

Adds the class `AppLauncher` which takes configuration arguments to the
Isaac Sim `SimulationApp` and several environment variables. It launches
the SimulationApp and corresponding extensions in a controlled manner
allowing users to decide between different remote deployments, ROS
bridges, and viewport rendering.

AppLauncher can then be queried for logic on other SimulationApp
operations e.g. whether or not `SimulationContext.step()` should render
or not based on the resolved flags `AppLauncher.VIEWPORT` and
`AppLauncher.RENDER`.

Fixes #32 

## Type of change

- New feature (non-breaking change which adds functionality)
- This change requires a documentation update

## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./orbit.sh --format`
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have updated the changelog and the corresponding version in the
extension's `config/extension.toml` file

---------

Co-authored-by: Farbod Farshidian <ffarshidian@theaiinstitute.com>
Co-authored-by: Mayank Mittal <mittalma@leggedrobotics.com>
Mayankm96 added a commit that referenced this pull request Dec 22, 2023
…ent variables (#33)

# Description

Adds the class `AppLauncher` which takes configuration arguments to the
Isaac Sim `SimulationApp` and several environment variables. It launches
the SimulationApp and corresponding extensions in a controlled manner
allowing users to decide between different remote deployments, ROS
bridges, and viewport rendering.

AppLauncher can then be queried for logic on other SimulationApp
operations e.g. whether or not `SimulationContext.step()` should render
or not based on the resolved flags `AppLauncher.VIEWPORT` and
`AppLauncher.RENDER`.

Fixes #32 

## Type of change

- New feature (non-breaking change which adds functionality)
- This change requires a documentation update

## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./orbit.sh --format`
- [x] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have updated the changelog and the corresponding version in the
extension's `config/extension.toml` file

---------

Co-authored-by: Farbod Farshidian <ffarshidian@theaiinstitute.com>
Co-authored-by: Mayank Mittal <mittalma@leggedrobotics.com>
elin-bdai pushed a commit to fyu-bdai/IsaacLab that referenced this pull request Feb 11, 2025
* fix history resent for all groups

* tested fix
sbtc-sipbb pushed a commit to Swiss-Battery-Technology-Center/IsaacLab that referenced this pull request Jul 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant