-
Notifications
You must be signed in to change notification settings - Fork 22
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
fix: in cgAdd: make cgLayer be optional #182
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #182 +/- ##
==========================================
+ Coverage 82.03% 82.16% +0.13%
==========================================
Files 14 14
Lines 729 729
Branches 140 166 +26
==========================================
+ Hits 598 599 +1
+ Misses 130 129 -1
Partials 1 1 ☔ View full report in Codecov by Sentry. |
I don't know if we as library maintainers are allowed to make such assumptions. Loading a template before playing it certainly does not seem like such a crazy idea. I'm definitely not against it, it would be useful for most of what I do too but it feels like a dangerous decision to make. |
I think I do agree that maybe it would be better for |
f1fa99e
to
0385790
Compare
0385790
to
3066ee3
Compare
Good points! |
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
quality of life improvement
What is the current behavior? (You can also link to an open issue here)
cgAdd requires the parameters
cgLayer
andplayOnLoad
cgLayer
is optional and defaults to1
playOnLoad
is optional and defaults totrue
In my experience,
cgLayer
andplayOnLoad
are rarely used nowadays, so I think that we should allow for leaving them out and fill in the most-commonly used values.