Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds a validity check for configclasses #1214

Merged
merged 63 commits into from
Oct 23, 2024

Conversation

Dhoeller19
Copy link
Collaborator

@Dhoeller19 Dhoeller19 commented Oct 11, 2024

Description

Added a mechanism to check for the validity of a configclass object.
A configclass object is valid if it contains no MISSING attributes.

Type of change

  • New feature (non-breaking change which adds functionality)

Checklist

  • I have run the pre-commit checks with ./isaaclab.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
  • I have added my name to the CONTRIBUTORS.md or my name already exists there

Copy link
Contributor

@lgulich lgulich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm, ooi did you ever consider to use pydantic for this? It could probably do many things out of the box but may not be flexible enough for some very advanced use cases.

@Mayankm96 Mayankm96 added the enhancement New feature or request label Oct 11, 2024
Dhoeller19 and others added 2 commits October 14, 2024 11:46
…ass.py

Co-authored-by: Mayank Mittal <12863862+Mayankm96@users.noreply.github.com>
Signed-off-by: David Hoeller <dhoeller@nvidia.com>
…ass.py

Co-authored-by: Mayank Mittal <12863862+Mayankm96@users.noreply.github.com>
Signed-off-by: David Hoeller <dhoeller@nvidia.com>
…in_importer_cfg.py

Co-authored-by: Mayank Mittal <12863862+Mayankm96@users.noreply.github.com>
Signed-off-by: David Hoeller <dhoeller@nvidia.com>
Copy link
Contributor

@Mayankm96 Mayankm96 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine. A huge MR but the changes just had to be rolled out everywhere so it's okay (not ideal though).

only concern left is ray-caster change. Would be great to isolate these changes because they can't be "clubbed" into other changes...

Co-authored-by: Mayank Mittal <12863862+Mayankm96@users.noreply.github.com>
Signed-off-by: David Hoeller <dhoeller@nvidia.com>
@Dhoeller19 Dhoeller19 merged commit bd4cd3b into main Oct 23, 2024
5 checks passed
@Dhoeller19 Dhoeller19 deleted the feature/check_configclass_validity branch October 23, 2024 07:43
iamdrfly pushed a commit to iamdrfly/IsaacLab that referenced this pull request Nov 21, 2024
# Description

Added a mechanism to check for the validity of a configclass object.
A configclass object is valid if it contains no MISSING attributes.

## Type of change

- New feature (non-breaking change which adds functionality)

## Checklist

- [x] I have run the [`pre-commit` checks](https://pre-commit.com/) with
`./isaaclab.sh --format`
- [ ] I have made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [x] 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
- [x] I have added my name to the `CONTRIBUTORS.md` or my name already
exists there
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.

3 participants