-
Notifications
You must be signed in to change notification settings - Fork 893
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
Normalize entity same index as base entity #681
Conversation
docs/source/changelog.rst
Outdated
@@ -11,6 +11,7 @@ Changelog | |||
* Set index after adding ancestor relationship variables (:pr:`668`) | |||
* Fix user-supplied variable_types modification in Entity init (:pr:`675`) | |||
* Don't calculate dependencies of unnecessary features (:pr:`667`) | |||
* Normalize entity same index as base entity #681 (:pr:`681`) |
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.
The ":pr:681" syntax will create a link to this pr, you can remove the "#681". Also can you add a little more to the description so someone unfamiliar could grasp the issue?
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.
Looks good!
Codecov Report
@@ Coverage Diff @@
## master #681 +/- ##
==========================================
+ Coverage 97.44% 97.44% +<.01%
==========================================
Files 118 118
Lines 9634 9643 +9
==========================================
+ Hits 9388 9397 +9
Misses 246 246
Continue to review full report at Codecov.
|
This request addresses #670 .
Adds a check and raises an exception if the index of the base entity is equal to the index argument. This request adds an accompanying test case.
As stated in #670, Feature tools does not handle one-to-one relationships in entitysets. Therefore, this check must be made to stop creating a one-to-one relationship with the same index.