Skip to content

Add ability for python measurement services to have multiple user interface files #102

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

Merged
merged 18 commits into from
Oct 18, 2022

Conversation

dixonjoel
Copy link
Collaborator

What does this Pull Request accomplish?

Metadata was changed recently to allow a service to specify multiple UI files. This updates the templates and the grpc service to allow multiple UI file paths. Also updating the sample measurement to specify and include two .measui files which are slightly different to demonstrate this and also to expand the test so it's asserting both .measui files exist.

Why should this Pull Request be merged?

Add ability for multiple .measui files to the Python repo.

What testing has been done?

Automated tests plus running the sample measurement with the feature toggle on for switching between multiple .measui files and running with that.

@dixonjoel
Copy link
Collaborator Author

@bkeryan I did not yet update all the examples with their .lock files because I understood we have to publish a release, then update the .lock files to reference the new release. However, did we say that we were going to add the .lock files to the .gitignore and not distribute them? If that's the case, it seems like we won't have to wait to update the examples to use multiple ui-file-paths and we can (not sure it's a good idea or a separate PR is better anyway) do it all in this one change? Key point being we don't have to wait for a new published release of ni-measurement-service to change the examples.

@bkeryan bkeryan closed this Oct 17, 2022
@bkeryan bkeryan reopened this Oct 17, 2022
@bkeryan
Copy link
Collaborator

bkeryan commented Oct 17, 2022

@bkeryan I did not yet update all the examples with their .lock files because I understood we have to publish a release, then update the .lock files to reference the new release. However, did we say that we were going to add the .lock files to the .gitignore and not distribute them? If that's the case, it seems like we won't have to wait to update the examples to use multiple ui-file-paths and we can (not sure it's a good idea or a separate PR is better anyway) do it all in this one change? Key point being we don't have to wait for a new published release of ni-measurement-service to change the examples.

Yes, I've been meaning to get back to that. Ignore the lock files for this PR.

@mshafer-NI
Copy link
Collaborator

mshafer-NI commented Oct 17, 2022 via email

@dixonjoel dixonjoel merged commit 9a401e5 into main Oct 18, 2022
@dixonjoel dixonjoel deleted the users/jdixon/multiple-user-interfaces branch October 18, 2022 16:26
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.

3 participants