-
Notifications
You must be signed in to change notification settings - Fork 103
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
Switch to emmet's MoleculeMetadata
#301
Conversation
MoleculeMetadata
MoleculeMetadata
@utf: This should be ready to merge. If you wouldn't mind bumping the version after this merge sometime, that'd be a great help! @nwinner: You use the |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #301 +/- ##
==========================================
- Coverage 65.93% 65.57% -0.36%
==========================================
Files 73 72 -1
Lines 7051 7018 -33
Branches 899 896 -3
==========================================
- Hits 4649 4602 -47
- Misses 2137 2150 +13
- Partials 265 266 +1
|
Update unit tests isort+black lint fix Fix cp2k inheritance of moleculemetadata lint fix Update emmet Update emmet Fix unit test Update to match emmet isort+black Remove unused kwarg Fix cclib test Undo enums formatting Undo enums formatting
@utf, could you give this a look when you get the chance? Thanks! |
This looks great. Thanks Andrew |
Ah there are some unresolved conflicts apparently. |
Taken care of now, boss. Feel free to merge at your discretion! |
Thanks! |
Addresses #300, wherein I realized we had a
MoleculeMetadata
schema in both Atomate2 and emmet, resulting in near-duplicate blocks of code. I merged the two together in emmet here and updated Atomate2 to use emmet'sMoleculeMetadata
instead just like you did forStructureData
. This should consolidate things within Atomate2 nicely. It's also coincidentally in line with Alex's recent efforts to move some more general schema things to emmet.Edit: We get about 250 lines out of Atomate2 and into emmet (where they belong), which I consider a win.