Skip to content
This repository was archived by the owner on Nov 6, 2019. It is now read-only.

Conversation

@1mike12
Copy link

@1mike12 1mike12 commented Oct 3, 2016

No description provided.

.gitignore Outdated
npm-debug.log

.idea
!.idea/codeStyleSettings.xml
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@1mike12 This seems like the kind of thing that belongs in your .gitignore_global file (run git config --get core.excludesfile for the path), not specific repos. Everyone uses a different editor and .gitignore files would get out of control of they had to accommodate everyone's setup.
(I also use Webstorm, FWIW, and have .idea in my ~/.global_gitignore.)

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no you're totally right, I wasn't thinking and rushed the push up. thanks for the tip


if (key === "UserDeliveryPreferenceArray"){
//add an exception for this since the ArrayName and Key name are incongruent
parentObj[newKey] = _.compact(parentObj[key][0]["NotificationEnable"])
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I'm assuming this is for https://www.developer.ebay.com/Devzone/XML/docs/Reference/eBay/GetNotificationPreferences.html#Response.UserDeliveryPreferenceArray ?)

This seems reasonable enough. It's a shame this module has to have so much crazy parsing code, but it's mostly because the source data it's dealing with is often structured bizarrely.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah it is. I think as gross as it is, if someone else wants to take a stab at it, then you gave them the option to make their own parser, and yes, it's ebay's fault for being so inconsistent.

Copy link
Owner

@benbuckman benbuckman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@1mike12 I'm inclined to merge the parsing change but not the .gitignore change for the reasons mentioned inline.
Please let me know if you disagree.
Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants