-
Notifications
You must be signed in to change notification settings - Fork 14
Invalid tag modification v2 #149
base: master
Are you sure you want to change the base?
Conversation
|
@bkowshik @amishas157 - is this good to merge? any next actions? |
|
Sorry @bkowshik , got late for reviewing this PR. Will be reviewing this PR by today and see the next actions here. |
|
|
||
|
|
||
| function invalidTagModification(newVersion, oldVersion, callback) { | ||
| var result = {}; |
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.
|
|
||
| function invalidTagModification(newVersion, oldVersion, callback) { | ||
| var result = {}; | ||
| if (!newVersion || !oldVersion) return callback(null, result); |
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.
Now we assume that newVersion will always be present in a geojson. And if a feature is deleted, we will check for deleted tag of new version. Ref commit : 2e0e6b6
So (!newVersion || !oldVersion) will become (newVersion.deleted || !oldVersion)
@bkowshik By that did you mean should we catch feature only when its one and only primary tag is deleted from it? |
Uses learning's from #147 to implement:
relation@amishas157 the PR also has a script to scrape data and a Jupyter notebook with all the analysis. It is ok if you review just the comparator and tests.