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

Avoid type ambivalence in Experiment.screen and Experiment.eyetracker #891

Open
4 tasks done
saeub opened this issue Nov 9, 2024 · 1 comment
Open
4 tasks done
Labels
bug Something isn't working good first issue Good for newcomers nonessential nice to have

Comments

@saeub
Copy link
Collaborator

saeub commented Nov 9, 2024

Current Behavior

At least Experiment.eyetracker can be None (if sampling_rate is passed in Experiment.__init__()). Experiment.screen should always be of type Screen, unless it is tampered with after initialization.

Details: #884 (comment)

Expected Behavior

Experiment.screen should always be of type Screen, Experiment.eyetracker should alwys be of type EyeTracker.

Minimum acceptance criteria

  • Implement Experiment.screen and Experiment.eyetracker as non-null properties.

  • Remove unnecessary None check in from_asc() (see feat: Store metadata from ASC in experiment metadata #884 (comment))

  • I am running the latest version

  • I checked the documentation and found no answer

  • I checked to make sure that this issue has not already been filed

  • I have provided sufficient information for the team

@saeub saeub added the bug Something isn't working label Nov 9, 2024
@dkrako dkrako added good first issue Good for newcomers nonessential nice to have labels Dec 11, 2024
@dkrako
Copy link
Contributor

dkrako commented Dec 11, 2024

I labeled it nonessential as it's only protecting the user against themselves. feel free to raise the priority in case

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers nonessential nice to have
Projects
None yet
Development

No branches or pull requests

3 participants
@dkrako @saeub and others