10BC0 Fallback to _response_dict if _rootkey is not present in response dict by Anmol-Gulati · Pull Request #71 · python-amazon-mws/python-amazon-mws · GitHub
[go: up one dir, main page]

Skip to content
This repository was archived by the owner on Jan 4, 2025. It is now read-only.

Conversation

@Anmol-Gulati
Copy link
Contributor
@Anmol-Gulati Anmol-Gulati commented May 18, 2018

This is the case while fetching some of the reports. I particularly found this
in 'GET_XML_RETURNS_DATA_BY_RETURN_DATE'. In this case, the data is returned
but not in rootkey. This will at least let the user parse the data on their own

GriceTurrble and others added 11 commits February 4, 2018 10:42
* Added Finances API Feature

* .setup.py: bump version to 0.7.5-dev0

* Split out request_description building from make_request()

So that it can be tested more easily, and refactored

* Split out building the initial params dict from make_request()

So that it can be tested more easily

* Add fake MWS credentials pytest fixture

* test_service_status() should use the pytest fake credentials fixture

* Add more pytest fixtures (access_key, secret_key, account_id, timestamp)

* Add test for calc_request_description()

* Split out calc_request_description() into more statements

So that it is easier to debug

* Fix calc_request_description - don't include leading ampersand

* Don't do automated deployments via Travis (for the moment)

* Update README.md badges

* InboundShipments, next_token_action decorator, and some style cleanups. (python-amazon-mws#33)

* Testing out git commits from VS Code

* Reverting the test commit

* Adding VS Code settings to gitignore.

* Style fixes

* MWS.enumerate_param deprecated: now using utils.enumerate_param and utils.enumerate_params

* InboundShipments fleshed out; added `utils.next_token_action` decorator; deprecated separate methods for `...by_next_token()`

* Bugfix, rename `_enumerate_param` to `enumerate_param` (no need for private)

* Fix for next_token issues.

* TravisCI flake8 complaining, fixes.

* Minor flake8 complaint.

* Hack to get flake8 to stop complaining.

* Strip pylint disables to clear line length issue.

* Correction to keyed params, now tests every item in values sequence to ensure all are dicts.

* Add tests for param methods in utils.

* Add test for next token decorator.

* Adding 'InboundShipments' to `__all__`

* Assigning response a default in __init__ for DictWrapper and DataWrapper

* Unneeded line breaks removed + docstring formatting

* Comment corrected. They're tuples, not sets.

* Finances methods updated to use next_token_action decorator

* Create .travis.yaml

* Update .gitignore

* Removing deploy code from local travis

* Delete .travis.yaml

* Pushed to 0.8.0-dev0

Recently added functionality to InboundShipments, as well as Finances API. These constitute feature additions with backwards compatibility, which calls for a minor version update.

* Adding Python 3.6 category

We are testing in 3.6 in Travis anyway. May as well include the note.

* Specified master and develop branches for badges

Ensured the badges for Travis and Codecov are pointing to the appropriate branches (used to be pointing to default, which was master in both cases).

* Updated comments throughout module

No substantial code changes, comment changes only. Also ensured all docstrings follow same format.

* Fixed docstring formatting

Also made slight update to docstring for ObjectDict to more clearly note what it does, vs what the original code did.

* Fix for flake8 (trailing whitespace)

* Fix for flake8 (trailing whitespace)

* Bump to 0.8.0 (drop dev tag) for release

* Bug: Incorrect use of `super` for back-compat

Using the old-style `super` syntax to comply with Python 2.7 compatibility. Not revealed in tests, because current tests don't touch the APIs. Whoops!

* Added back old object names in case needed

Old names `object_dict` and `xml2dict` added back in case the old objects are being used directly by some users.

To be removed in 1.0.0 release down the road.
Remove old-style string formatting for sake of clarity.
* version bump

* No from_address assignment needed in Inbound init

Similar fix as commit on `develop`, which will come in with 1.0 release.

Also, version bump for new bugfix release.
This is the case while fetching some of the reports. I particularly found this
in '_GET_XML_RETURNS_DATA_BY_RETURN_DATE_'. In this case the data is returned
but not in rootkey. This will at least let the user parse the data on there own
@codecov-io
Copy link
codecov-io commented May 18, 2018

Codecov Report

Merging #71 into master will not change coverage.
The diff coverage is 0%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #71   +/-   ##
=======================================
  Coverage   46.67%   46.67%           
=======================================
  Files           4        4           
  Lines         632      632           
  Branches       64       64           
=======================================
  Hits          295      295           
+ Misses        324      322    -2     
- Partials       13       15    +2
Impacted Files Coverage Δ
mws/mws.py 44.6% <0%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6c67339...baac4a8. Read the comment docs.

@Anmol-Gulati
Copy link
Contributor Author

@GriceTurrble requesting review

@GriceTurrble GriceTurrble changed the base branch from master to develop May 19, 2018 21:14
@GriceTurrble
Copy link
Member

@Anmol-Gulati The change is minimal enough that it shouldn't impact other use cases, so long as it fixes the issue in question.

That said, PRs must be requested to the develop branch. On switching branches, the merge conflict for this PR is too complex.

Please open a new PR by making the change to a fork of the develop branch. Apologies for the inconvenience.

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.

4 participants

0