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

Make DataSet.paramspecs always return ParamSpec's #1720

Merged
merged 3 commits into from
Sep 19, 2019

Conversation

astafan8
Copy link
Contributor

... not ParamSpecBase's.

This was introduced some time ago when parameter info
was not written to database until the dataset is started.
This is an interface inconsistency, originally this DataSet
property was returning ParamSpec's.

... not ParamSpecBase's

This was introduced some time ago when parameter info
was not written to database until the dataset is started.
This is an interface inconsistency, originally this DataSet
property was returning ParamSpec's.
@astafan8 astafan8 marked this pull request as ready for review September 13, 2019 20:47
@codecov
Copy link

codecov bot commented Sep 18, 2019

Codecov Report

Merging #1720 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1720      +/-   ##
==========================================
+ Coverage   67.22%   67.31%   +0.09%     
==========================================
  Files         146      146              
  Lines       18005    18074      +69     
==========================================
+ Hits        12103    12167      +64     
- Misses       5902     5907       +5

@jenshnielsen jenshnielsen merged commit 9ce3ee3 into master Sep 19, 2019
@jenshnielsen jenshnielsen deleted the dataset-paramspecs-to-return-paramspecs-only branch September 19, 2019 07:16
@jenshnielsen
Copy link
Collaborator

@astafan8 Is there any reason that you created this feature branch on qcodes/qcodes and not on your fork?

@astafan8
Copy link
Contributor Author

Is there any reason that you created this feature branch on qcodes/qcodes and not on your fork?

@jenshnielsen mostly out of laziness, i made the change using the github website. and after merging i always delete these branches (thanks for doing that for me now).

@jenshnielsen
Copy link
Collaborator

Ok that's fine as long as you are sure that you remember to delete the branch. I know from previous experience that it's easy to forget

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants