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

Parse fully qualified comp instance name in JSON loaders #178

Merged
merged 4 commits into from
Aug 14, 2024

Conversation

jwest115
Copy link
Collaborator

Related Issue(s) nasa/fpp#349, nasa/fprime#2813
Has Unit Tests (y/n)
Documentation Included (y/n)

Change Description

As part of nasa/fpp#349, command, events, telemetry channel, etc. names are now fully qualified in the JSON dictionary. This PR updates how we parse the component instance names in the comment, event, and channel JSON loaders so that the fully qualified name is included.

Rationale

Needed for compatibility with nasa/fpp#349

Testing/Review Recommendations

Ran FPrime Ref deployment and tested it with changes introduced in this PR. Confirmed that the command, event, and channel names are fully qualified. Was able to successfully send commands and filter commands/telemetry.

update spelling
Copy link
Collaborator

@thomas-bc thomas-bc left a comment

Choose a reason for hiding this comment

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

Looks good to me!
Could you also update the test cases in https://github.com/nasa/fprime-gds/blob/devel/test/fprime_gds/common/loaders/test_json_loader.py to include a qualified name for its associated Ref dictionary (provided in the test folder)?

@jwest115
Copy link
Collaborator Author

jwest115 commented Aug 8, 2024

Thanks @thomas-bc. I updated the JSON loader test and Ref dictionary to include the qualified names.

@jwest115 jwest115 merged commit c926d86 into nasa:devel Aug 14, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants