[FIX] don't use private fields, use the API #35
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
👍 |
hbrunn
force-pushed
the
8.0-l10n_nl_postcodeapi-fix_private
branch
from
f21115e
to
5a06ac2
Compare
|
👍 |
StefanRijnhart
added a commit
that referenced
this pull request
Mar 1, 2016
[FIX] don't use private fields, use the API
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
version 0.2 of the postcode api supports as well protocol version 1 as 2, and in version 2, the internal data structures are different. By sticking to what the API offers, the addons works in both cases.