-
Notifications
You must be signed in to change notification settings - Fork 631
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
poly_to_angles
fixing #6978
#6979
Conversation
Hello. You may have forgotten to update the changelog!
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6979 +/- ##
=======================================
Coverage 99.59% 99.60%
=======================================
Files 484 484
Lines 46193 46193
=======================================
+ Hits 46008 46009 +1
+ Misses 185 184 -1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, thanks @KetpuntoG 🙌
LGTM!
Co-authored-by: David Wierichs <[email protected]>
Co-authored-by: Soran Jahangiri <[email protected]>
…ennylane into poly_to_angles_fix
Co-authored-by: Utkarsh <[email protected]>
…ennylane into poly_to_angles_fix
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
Before submitting
Please complete the following checklist when submitting a PR:
All new features must include a unit test.
If you've fixed a bug or added code that should be tested, add a test to the
test directory!
All new functions and code must be clearly commented and documented.
If you do make documentation changes, make sure that the docs build and
render correctly by running
make docs
.Ensure that the test suite passes, by running
make test
.Add a new entry to the
doc/releases/changelog-dev.md
file, summarizing thechange, and including a link back to the PR.
The PennyLane source code conforms to
PEP8 standards.
We check all of our code against Pylint.
To lint modified files, simply
pip install pylint
, and thenrun
pylint pennylane/path/to/file.py
.When all the above are checked, delete everything above the dashed
line and fill in the pull request template.
Context:
[sc-84735]
Description of the Change:
Now we copy the input into a list
Benefits:
It works with any interface
Possible Drawbacks:
Related GitHub Issues:
#6978