mercadopago-sdk 0.3.6 → 2.0.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (127) hide show
  1. checksums.yaml +5 -5
  2. data/.editorconfig +10 -0
  3. data/.github/ISSUE_TEMPLATE/bug_report.md +28 -0
  4. data/.github/ISSUE_TEMPLATE/feature_request.md +19 -0
  5. data/.github/workflows/ruby.yml +35 -0
  6. data/.gitignore +2 -1
  7. data/.rubocop.yml +1 -0
  8. data/.rubocop_todo.yml +104 -0
  9. data/.ruby-version +1 -0
  10. data/CODE_OF_CONDUCT.md +74 -0
  11. data/CODING_GUIDELINES.md +70 -0
  12. data/CONTRIBUTING.md +57 -0
  13. data/Gemfile +8 -0
  14. data/Gemfile.lock +51 -12
  15. data/LICENSE.txt +21 -0
  16. data/README.md +54 -143
  17. data/Rakefile +3 -1
  18. data/docs/CODE_OF_CONDUCT_md.html +154 -0
  19. data/docs/CODING_GUIDELINES_md.html +188 -0
  20. data/docs/CONTRIBUTING_md.html +165 -0
  21. data/docs/LICENSE_txt.html +96 -0
  22. data/docs/Mercadopago.html +123 -0
  23. data/docs/Mercadopago/AdvancedPayment.html +279 -0
  24. data/docs/Mercadopago/Card.html +204 -0
  25. data/docs/Mercadopago/CardToken.html +160 -0
  26. data/docs/Mercadopago/Config.html +266 -0
  27. data/docs/Mercadopago/Customer.html +228 -0
  28. data/docs/Mercadopago/DisbursementRefund.html +183 -0
  29. data/docs/Mercadopago/HttpClient.html +249 -0
  30. data/docs/Mercadopago/IdentificationType.html +136 -0
  31. data/docs/Mercadopago/MPBase.html +316 -0
  32. data/docs/Mercadopago/MerchantOrder.html +209 -0
  33. data/docs/Mercadopago/Payment.html +208 -0
  34. data/docs/Mercadopago/PaymentMethods.html +136 -0
  35. data/docs/Mercadopago/Preference.html +184 -0
  36. data/docs/Mercadopago/Refund.html +160 -0
  37. data/docs/Mercadopago/RequestOptions.html +433 -0
  38. data/docs/Mercadopago/SDK.html +528 -0
  39. data/docs/Mercadopago/User.html +136 -0
  40. data/docs/README_md.html +181 -0
  41. data/docs/created.rid +25 -0
  42. data/docs/css/fonts.css +167 -0
  43. data/docs/css/rdoc.css +619 -0
  44. data/docs/fonts/Lato-Light.ttf +0 -0
  45. data/docs/fonts/Lato-LightItalic.ttf +0 -0
  46. data/docs/fonts/Lato-Regular.ttf +0 -0
  47. data/docs/fonts/Lato-RegularItalic.ttf +0 -0
  48. data/docs/fonts/SourceCodePro-Bold.ttf +0 -0
  49. data/docs/fonts/SourceCodePro-Regular.ttf +0 -0
  50. data/docs/images/add.png +0 -0
  51. data/docs/images/arrow_up.png +0 -0
  52. data/docs/images/brick.png +0 -0
  53. data/docs/images/brick_link.png +0 -0
  54. data/docs/images/bug.png +0 -0
  55. data/docs/images/bullet_black.png +0 -0
  56. data/docs/images/bullet_toggle_minus.png +0 -0
  57. data/docs/images/bullet_toggle_plus.png +0 -0
  58. data/docs/images/date.png +0 -0
  59. data/docs/images/delete.png +0 -0
  60. data/docs/images/find.png +0 -0
  61. data/docs/images/loadingAnimation.gif +0 -0
  62. data/docs/images/macFFBgHack.png +0 -0
  63. data/docs/images/package.png +0 -0
  64. data/docs/images/page_green.png +0 -0
  65. data/docs/images/page_white_text.png +0 -0
  66. data/docs/images/page_white_width.png +0 -0
  67. data/docs/images/plugin.png +0 -0
  68. data/docs/images/ruby.png +0 -0
  69. data/docs/images/tag_blue.png +0 -0
  70. data/docs/images/tag_green.png +0 -0
  71. data/docs/images/transparent.png +0 -0
  72. data/docs/images/wrench.png +0 -0
  73. data/docs/images/wrench_orange.png +0 -0
  74. data/docs/images/zoom.png +0 -0
  75. data/docs/index.html +109 -0
  76. data/docs/js/darkfish.js +84 -0
  77. data/docs/js/navigation.js +105 -0
  78. data/docs/js/navigation.js.gz +0 -0
  79. data/docs/js/search.js +110 -0
  80. data/docs/js/search_index.js +1 -0
  81. data/docs/js/search_index.js.gz +0 -0
  82. data/docs/js/searcher.js +229 -0
  83. data/docs/js/searcher.js.gz +0 -0
  84. data/docs/table_of_contents.html +562 -0
  85. data/lib/mercadopago.rb +24 -349
  86. data/lib/mercadopago/config/config.rb +42 -0
  87. data/lib/mercadopago/config/request_options.rb +85 -0
  88. data/lib/mercadopago/core/mp_base.rb +77 -0
  89. data/lib/mercadopago/http/http_client.rb +74 -0
  90. data/lib/mercadopago/resources/advanced_payment.rb +48 -0
  91. data/lib/mercadopago/resources/card.rb +31 -0
  92. data/lib/mercadopago/resources/card_token.rb +19 -0
  93. data/lib/mercadopago/resources/customer.rb +36 -0
  94. data/lib/mercadopago/resources/disbursement_refund.rb +24 -0
  95. data/lib/mercadopago/resources/identification_type.rb +13 -0
  96. data/lib/mercadopago/resources/merchant_order.rb +32 -0
  97. data/lib/mercadopago/resources/payment.rb +35 -0
  98. data/lib/mercadopago/resources/payment_methods.rb +13 -0
  99. data/lib/mercadopago/resources/preference.rb +26 -0
  100. data/lib/mercadopago/resources/refund.rb +24 -0
  101. data/lib/mercadopago/resources/user.rb +13 -0
  102. data/lib/mercadopago/sdk.rb +85 -0
  103. data/mercadopago.gemspec +15 -15
  104. data/tests/test_card.rb +79 -0
  105. data/tests/test_card_token.rb +39 -0
  106. data/tests/test_customer.rb +54 -0
  107. data/tests/test_identification_type.rb +16 -0
  108. data/tests/test_merchant_order.rb +94 -0
  109. data/tests/test_payment.rb +102 -0
  110. data/tests/test_payment_methods.rb +14 -0
  111. data/tests/test_preference.rb +49 -0
  112. data/tests/test_refund.rb +88 -0
  113. data/tests/test_user.rb +17 -0
  114. data/tests/tests.rb +12 -56
  115. metadata +154 -37
  116. data/examples/checkout-buttons/basic_preference/button.rb +0 -28
  117. data/examples/instant-payment-notifications/receive-ipn.rb +0 -25
  118. data/examples/payment-search/search-approved-payments.rb +0 -23
  119. data/examples/payment-search/search-creditcard-payments.rb +0 -23
  120. data/examples/payment-search/search-funded-payments-by-name.rb +0 -23
  121. data/examples/payment-search/search-payments-from-email-and-date.rb +0 -23
  122. data/examples/payment-search/search-payments.rb +0 -23
  123. data/examples/preapproval-payments/button.rb +0 -42
  124. data/lib/ssl_options_patch.rb +0 -15
  125. data/lib/version.rb +0 -1
  126. data/mercadopago-sdk-0.3.2.gem +0 -0
  127. data/mercadopago-sdk-0.3.3.gem +0 -0
data/docs/CODING_GUIDELINES_md.html ADDED
@@ -0,0 +1,188 @@
1
+ <!DOCTYPE html>
2
+
3
+ <html>
4
+ <head>
5
+ <meta charset="UTF-8">
6
+
7
+ <title>CODING_GUIDELINES - RDoc Documentation</title>
8
+
9
+ <script type="text/javascript">
10
+ var rdoc_rel_prefix = "./";
11
+ var index_rel_prefix = "./";
12
+ </script>
13
+
14
+ <script src="./js/navigation.js" defer></script>
15
+ <script src="./js/search.js" defer></script>
16
+ <script src="./js/search_index.js" defer></script>
17
+ <script src="./js/searcher.js" defer></script>
18
+ <script src="./js/darkfish.js" defer></script>
19
+
20
+ <link href="./css/fonts.css" rel="stylesheet">
21
+ <link href="./css/rdoc.css" rel="stylesheet">
22
+
23
+
24
+ <body id="top" role="document" class="file">
25
+ <nav role="navigation">
26
+ <div id="project-navigation">
27
+ <div id="home-section" role="region" title="Quick navigation" class="nav-section">
28
+ <h2>
29
+ <a href="./index.html" rel="home">Home</a>
30
+ </h2>
31
+
32
+ <div id="table-of-contents-navigation">
33
+ <a href="./table_of_contents.html#pages">Pages</a>
34
+ <a href="./table_of_contents.html#classes">Classes</a>
35
+ <a href="./table_of_contents.html#methods">Methods</a>
36
+ </div>
37
+ </div>
38
+
39
+ <div id="search-section" role="search" class="project-section initially-hidden">
40
+ <form action="#" method="get" accept-charset="utf-8">
41
+ <div id="search-field-wrapper">
42
+ <input id="search-field" role="combobox" aria-label="Search"
43
+ aria-autocomplete="list" aria-controls="search-results"
44
+ type="text" name="search" placeholder="Search" spellcheck="false"
45
+ title="Type to search, Up and Down to navigate, Enter to load">
46
+ </div>
47
+
48
+ <ul id="search-results" aria-label="Search Results"
49
+ aria-busy="false" aria-expanded="false"
50
+ aria-atomic="false" class="initially-hidden"></ul>
51
+ </form>
52
+ </div>
53
+
54
+ </div>
55
+
56
+
57
+ <div class="nav-section">
58
+ <h3>Table of Contents</h3>
59
+
60
+ <ul class="link-list" role="directory">
61
+ <li><a href="#label-Coding+Guidelines">Coding Guidelines</a>
62
+ <li><a href="#label-Language+Guidelines">Language Guidelines</a>
63
+ <li><a href="#label-Code+Guidelines">Code Guidelines</a>
64
+ <li><a href="#label-Comment+Guidelines">Comment Guidelines</a>
65
+ <li><a href="#label-Branching+Guidelines">Branching Guidelines</a>
66
+ <li><a href="#label-Git+Guidelines">Git Guidelines</a>
67
+ </ul>
68
+ </div>
69
+
70
+
71
+ <div id="project-metadata">
72
+
73
+ <div id="fileindex-section" class="nav-section">
74
+ <h3>Pages</h3>
75
+
76
+ <ul class="link-list">
77
+ <li><a href="./CODE_OF_CONDUCT_md.html">CODE_OF_CONDUCT</a>
78
+ <li><a href="./CODING_GUIDELINES_md.html">CODING_GUIDELINES</a>
79
+ <li><a href="./CONTRIBUTING_md.html">CONTRIBUTING</a>
80
+ <li><a href="./LICENSE_txt.html">LICENSE</a>
81
+ <li><a href="./README_md.html">README</a>
82
+ </ul>
83
+ </div>
84
+
85
+ </div>
86
+ </nav>
87
+
88
+ <main role="main" aria-label="Page CODING_GUIDELINES.md">
89
+
90
+ <h1 id="label-Coding+Guidelines">Coding Guidelines<span><a href="#label-Coding+Guidelines">&para;</a> <a href="#top">&uarr;</a></span></h1>
91
+
92
+ <p>The Mercado Pago Ruby SDK is a collaborative effort from the start. The SDK team thinks that contributions from different developer will enrich it&#39;s feature set and make it more relevant to the community.</p>
93
+
94
+ <p>However; absorbing all contributions as-is, while expedient, might lead to difficulties in maintenance of the codebase is left unchecked. Collaborative codebases often establish guidelines for contributors to ensure code remains maintainable over time. The effort to maintain the SDK is no different in this regard so a bit of guidance is in order.</p>
95
+
96
+ <p>The purpose of this guide is to set a baseline for contributions. These guidelines are not intended to limit the tools at your disposal nor to rewire the way you think but rather to encourage good neighbor behavior.</p>
97
+
98
+ <h2 id="label-Language+Guidelines">Language Guidelines<span><a href="#label-Language+Guidelines">&para;</a> <a href="#top">&uarr;</a></span></h2>
99
+
100
+ <p>We use <strong>english</strong> language. This is to be consistent everywhere, and to be considerate with developers that do not speak our native language.</p>
101
+
102
+ <p>Therefore: source code, comments, documentation, commit messages, review comments, and any other kind of contribution <em>MUST</em> use english language.</p>
103
+
104
+ <p>Typos are unavoidable, but try to reduce them by using a spellchecker. Most IDEs can be configured to run one automatically.</p>
105
+
106
+ <h2 id="label-Code+Guidelines">Code Guidelines<span><a href="#label-Code+Guidelines">&para;</a> <a href="#top">&uarr;</a></span></h2>
107
+ <ul><li>
108
+ <p>Set your IDE to follow the <a href="https://editorconfig.org/">.editorconfig</a> in each repository.</p>
109
+ </li><li>
110
+ <p>Follow the <a href="https://github.com/rubocop/ruby-style-guide">RuboCop Ruby Style Guide</a>.</p>
111
+ </li></ul>
112
+
113
+ <p>Generally speaking, be conscious when contributing and try following the same style that the code in the SDK already has. If you have any doubts, just ask us!</p>
114
+
115
+ <p>This rules will be enforced automatically when making a pull requests, and checks will fail if you do not follow them, resulting in your contribution being automatically rejected until fixed.</p>
116
+
117
+ <h2 id="label-Comment+Guidelines">Comment Guidelines<span><a href="#label-Comment+Guidelines">&para;</a> <a href="#top">&uarr;</a></span></h2>
118
+
119
+ <p>Comments in code are a hard thing to write, not because the words are difficult to produce but because it is hard to make relevant comments. Too much of it and people do not read comments (and it obfuscates code reading) and too little of it gives you no recourse but to read large portions of codebase to get insight as to what a feature/codeblock is doing. Both situations are undesirable and efforts should be made at all time to have a please comment reading experience</p>
120
+
121
+ <p>As a general rule you would have to comment on decisions you made while coding that are not part of any specification.</p>
122
+
123
+ <p>In particular you should always comment any decision that:</p>
124
+ <ul><li>
125
+ <p>Departs from common wisdom or convention (The <strong>why&#39;s</strong> are necessary).</p>
126
+ </li><li>
127
+ <p>Takes a significant amount of time to produce. A good rule of thumb here is that if you spent more than 1 hour thinking on how to produce a fragment of code that took 2 minutes of wrist time to write you should document your thinking to aid reader and allow for validation.</p>
128
+ </li><li>
129
+ <p>Need to preserve properties of the implementation. This is the case of performance sensitive portions of the codebase, goroutines synchronization, implementations of security primitives, congestion control algorithms, etc.</p>
130
+ </li></ul>
131
+
132
+ <p>As a general rule of what not to comment you should avoid:</p>
133
+ <ul><li>
134
+ <p>Commenting on structure of programs that is already part of a convention, specified or otherwise.</p>
135
+ </li><li>
136
+ <p>Having pedantic explanations of behavior that can be found by immediate examination of the surrounding code artifacts.</p>
137
+ </li><li>
138
+ <p>Commenting on behavior you cannot attest.</p>
139
+ </li></ul>
140
+
141
+ <h3 id="label-Branching+Guidelines">Branching Guidelines<span><a href="#label-Branching+Guidelines">&para;</a> <a href="#top">&uarr;</a></span></h3>
142
+
143
+ <p>Currently <code>master</code> is our only long term branch, below a few suggestions of short term branches naming:</p>
144
+ <ul><li>
145
+ <p><code>hotfix/something-needs-fix</code>: Small routine patches in code to features already there.</p>
146
+ </li><li>
147
+ <p><code>feature/something-new</code>: A new feature or a change in a existent feature. Beware of breaking changes that would require a major version bump.</p>
148
+ </li><li>
149
+ <p><code>doc/improves-documentation-for-this-feature</code>: If you add or change documentation with no impact to the source code.</p>
150
+ </li></ul>
151
+
152
+ <h3 id="label-Git+Guidelines">Git Guidelines<span><a href="#label-Git+Guidelines">&para;</a> <a href="#top">&uarr;</a></span></h3>
153
+
154
+ <p>All commits <strong>SHOULD</strong> follow the <a href="https://chris.beams.io/posts/git-commit">seven rules of a great Git commit message</a>:</p>
155
+ <ol><li>
156
+ <p>Separate subject from body with a blank line.</p>
157
+ </li><li>
158
+ <p>Limit the subject line to 72 characters.</p>
159
+ </li><li>
160
+ <p>Capitalize the subject line.</p>
161
+ </li><li>
162
+ <p>Do not end the subject line with a period.</p>
163
+ </li><li>
164
+ <p>Use the imperative mood in the subject line.</p>
165
+ </li><li>
166
+ <p>Wrap the body at 72 characters.</p>
167
+ </li><li>
168
+ <p>Use the body to explain what and why vs. how.</p>
169
+ </li></ol>
170
+
171
+ <p>Commits such as “fix tests”, “now it&#39;s working” and many other common messages we find usually in code <strong>WON&#39;T</strong> be accepted.</p>
172
+
173
+ <p>Ideally we would like to enforce these rules, but we are realistic and understand that it might be a big change for some people. So unless deviating heavily from what was stated we might accept your commits even if not following these rules perfectly.</p>
174
+
175
+ <p>Please avoid taking to much time to deliver code, and always <a href="https://git-scm.com/docs/git-rebase">rebase</a> your code to avoid reverse merge commits.</p>
176
+
177
+ <p>When reviewing, check if the PR adheres to <a href="https://github.com/rubocop/ruby-style-guide">RuboCop Ruby Style Guide</a>.</p>
178
+
179
+ </main>
180
+
181
+
182
+
183
+ <footer id="validator-badges" role="contentinfo">
184
+ <p><a href="https://validator.w3.org/check/referer">Validate</a>
185
+ <p>Generated by <a href="https://ruby.github.io/rdoc/">RDoc</a> 6.3.0.
186
+ <p>Based on <a href="http://deveiate.org/projects/Darkfish-RDoc/">Darkfish</a> by <a href="http://deveiate.org">Michael Granger</a>.
187
+ </footer>
188
+
data/docs/CONTRIBUTING_md.html ADDED
@@ -0,0 +1,165 @@
1
+ <!DOCTYPE html>
2
+
3
+ <html>
4
+ <head>
5
+ <meta charset="UTF-8">
6
+
7
+ <title>CONTRIBUTING - RDoc Documentation</title>
8
+
9
+ <script type="text/javascript">
10
+ var rdoc_rel_prefix = "./";
11
+ var index_rel_prefix = "./";
12
+ </script>
13
+
14
+ <script src="./js/navigation.js" defer></script>
15
+ <script src="./js/search.js" defer></script>
16
+ <script src="./js/search_index.js" defer></script>
17
+ <script src="./js/searcher.js" defer></script>
18
+ <script src="./js/darkfish.js" defer></script>
19
+
20
+ <link href="./css/fonts.css" rel="stylesheet">
21
+ <link href="./css/rdoc.css" rel="stylesheet">
22
+
23
+
24
+ <body id="top" role="document" class="file">
25
+ <nav role="navigation">
26
+ <div id="project-navigation">
27
+ <div id="home-section" role="region" title="Quick navigation" class="nav-section">
28
+ <h2>
29
+ <a href="./index.html" rel="home">Home</a>
30
+ </h2>
31
+
32
+ <div id="table-of-contents-navigation">
33
+ <a href="./table_of_contents.html#pages">Pages</a>
34
+ <a href="./table_of_contents.html#classes">Classes</a>
35
+ <a href="./table_of_contents.html#methods">Methods</a>
36
+ </div>
37
+ </div>
38
+
39
+ <div id="search-section" role="search" class="project-section initially-hidden">
40
+ <form action="#" method="get" accept-charset="utf-8">
41
+ <div id="search-field-wrapper">
42
+ <input id="search-field" role="combobox" aria-label="Search"
43
+ aria-autocomplete="list" aria-controls="search-results"
44
+ type="text" name="search" placeholder="Search" spellcheck="false"
45
+ title="Type to search, Up and Down to navigate, Enter to load">
46
+ </div>
47
+
48
+ <ul id="search-results" aria-label="Search Results"
49
+ aria-busy="false" aria-expanded="false"
50
+ aria-atomic="false" class="initially-hidden"></ul>
51
+ </form>
52
+ </div>
53
+
54
+ </div>
55
+
56
+
57
+ <div class="nav-section">
58
+ <h3>Table of Contents</h3>
59
+
60
+ <ul class="link-list" role="directory">
61
+ <li><a href="#label-Contributing+to+the+Mercado+Pago+Ruby+SDK">Contributing to the Mercado Pago Ruby SDK</a>
62
+ <li><a href="#label-How+to+contribute">How to contribute</a>
63
+ <li><a href="#label-Coding+Guidance">Coding Guidance</a>
64
+ <li><a href="#label-Request+For+Change+-2F+Feature+Request">Request For Change / Feature Request</a>
65
+ <li><a href="#label-Bug+Reports">Bug Reports</a>
66
+ <li><a href="#label-Pull+Request">Pull Request</a>
67
+ </ul>
68
+ </div>
69
+
70
+
71
+ <div id="project-metadata">
72
+
73
+ <div id="fileindex-section" class="nav-section">
74
+ <h3>Pages</h3>
75
+
76
+ <ul class="link-list">
77
+ <li><a href="./CODE_OF_CONDUCT_md.html">CODE_OF_CONDUCT</a>
78
+ <li><a href="./CODING_GUIDELINES_md.html">CODING_GUIDELINES</a>
79
+ <li><a href="./CONTRIBUTING_md.html">CONTRIBUTING</a>
80
+ <li><a href="./LICENSE_txt.html">LICENSE</a>
81
+ <li><a href="./README_md.html">README</a>
82
+ </ul>
83
+ </div>
84
+
85
+ </div>
86
+ </nav>
87
+
88
+ <main role="main" aria-label="Page CONTRIBUTING.md">
89
+
90
+ <h1 id="label-Contributing+to+the+Mercado+Pago+Ruby+SDK">Contributing to the Mercado Pago Ruby SDK<span><a href="#label-Contributing+to+the+Mercado+Pago+Ruby+SDK">&para;</a> <a href="#top">&uarr;</a></span></h1>
91
+
92
+ <p>Thank you for your interest in contributing to the Mercado Pago Ruby SDK!</p>
93
+
94
+ <h2 id="label-How+to+contribute">How to contribute<span><a href="#label-How+to+contribute">&para;</a> <a href="#top">&uarr;</a></span></h2>
95
+
96
+ <p>In order to contribute to the Mercado Pago Ruby SDK effectively we provide guidelines to address common case for contributions. Presently we have guides for the following type of changes.</p>
97
+ <ul><li>
98
+ <p>Request For Change (RFC) / Feature Request: These are suggestions / requests for features the SDK currently does not have. The SDK team evaluates these requests for adequacy / relevance / capacity and overall architectural consistency.</p>
99
+ </li><li>
100
+ <p>Bug Reports: These are reports of non compliant behavior with the SDK specification and other blatantly wrong behavior of the Mercado Pago Ruby SDK.</p>
101
+ </li></ul>
102
+
103
+ <p>In addition to contributing in the form of Bug Reports and RFCs it is also possible to contribute directly in code with a Pull Request (PR). In the case of a Pull Request you should also indicate the nature of the Pull Request (Feature/Bug/etc.) to help the team asses the Pull Request. If you are enthusiastic about a particular Feature being added or a bug being fixed, a PR is often the quickest way to promote your change as the team does not have to allocate as much resources to process the contribution.</p>
104
+
105
+ <p>In the case of PRs it is often best to consult with the SDK team before embarking on a PR, specially if it&#39;s a beefy one. Spending time on a PR that might later be rejected because major discrepancies with vision or competing contributions is an uncomfortable outcome for all involved people. Remember the SDK team with privilege overall consistency and progress over any one particular contribution.</p>
106
+
107
+ <h2 id="label-Coding+Guidance">Coding Guidance<span><a href="#label-Coding+Guidance">&para;</a> <a href="#top">&uarr;</a></span></h2>
108
+
109
+ <p>All contributions <em>MUST</em> follow the <a href="CODING_GUIDELINES.md">Coding Guidelines</a>. Contributions that fail to follow this guidelines will be disregarded and told to make the required modifications to do so.</p>
110
+
111
+ <h2 id="label-Request+For+Change+-2F+Feature+Request">Request For Change / Feature Request<span><a href="#label-Request+For+Change+-2F+Feature+Request">&para;</a> <a href="#top">&uarr;</a></span></h2>
112
+
113
+ <p>Generally speaking an RFC is needed when you want to add a new feature or change an existing one in an incompatible way that might result in a major version bump to the toolkit.</p>
114
+
115
+ <p>Though it seems a little bureaucratic, the process is in place in order to avoid frustration of a potential contributor by making the discussions take place before any code is written. Once the design and direction is fully agreed then the contributor can work peacefully knowing that their change will be committed.</p>
116
+
117
+ <p>As of this moment all you need to do is create an issue and use the <a href=".github/ISSUE_TEMPLATE/feature_request.md">Feature Request Template</a>.</p>
118
+
119
+ <p>Please prepend your issue title with <code>[RFC]</code> so that&#39;s easier to filter.</p>
120
+
121
+ <h2 id="label-Bug+Reports">Bug Reports<span><a href="#label-Bug+Reports">&para;</a> <a href="#top">&uarr;</a></span></h2>
122
+
123
+ <p>Bugs are a reality in software. We can&#39;t fix what we don&#39;t know about, so please report liberally. If you&#39;re not sure if something is a bug or not, feel free to file it anyway.</p>
124
+
125
+ <p>Before reporting a bug, please search existing issues and pull requests, as it&#39;s possible that someone else has already reported your error. In the off case that you find your issue as fixed/closed, please add a reference to it on your new one.</p>
126
+
127
+ <p>Your issue should contain a title and a clear description of the issue. You should also include as much relevant information as possible and a code sample that demonstrates the issue. The goal of a bug report is to make it easy for yourself - and others - to replicate the bug and develop a fix.</p>
128
+
129
+ <p>Opening an issue is as easy as following <a href="https://github.com/mercadopago/sdk-dotnet/issues/new">this link</a> and filling out the given template.</p>
130
+
131
+ <p>Bug reports may also be sent in the form of a <a href="#pull-request">pull request</a> containing a failing test.</p>
132
+
133
+ <h2 id="label-Pull+Request">Pull Request<span><a href="#label-Pull+Request">&para;</a> <a href="#top">&uarr;</a></span></h2>
134
+
135
+ <p>First and foremost: Source code, documentation, commit messages, review comments, and any other kind of contribution must <em>MUST</em> follow the <a href="CODING_GUIDELINES.md">Coding Guidelines</a>.</p>
136
+
137
+ <p>We use the “fork and pull” model <a href="https://help.github.com/articles/about-collaborative-development-models/">described here</a>, where contributors push changes to their personal fork and create pull requests to bring those changes into the source repository.</p>
138
+
139
+ <p>Your basic steps to get going:</p>
140
+ <ul><li>
141
+ <p>Fork the corresponding toolkit repository and create a branch from master for the issue you are working on.</p>
142
+ </li><li>
143
+ <p>Commit as you go following our git conventions.</p>
144
+ </li><li>
145
+ <p>Include tests that cover all non-trivial code. The existing tests should provide a template on how to test the toolkit correctly.</p>
146
+ </li><li>
147
+ <p>Make sure all test passes.</p>
148
+ </li><li>
149
+ <p>All code changes are expected to comply with the formatting style.</p>
150
+ </li><li>
151
+ <p>Push your commits to GitHub and create a pull request against the corresponding toolkit component master branch.</p>
152
+ </li></ul>
153
+
154
+ <p>If taking to much time to deliver code, <strong>always</strong> <a href="https://git-scm.com/docs/git-rebase">rebase</a> towards <code>master</code> before asking for a review, and avoid reverse merge commits.</p>
155
+
156
+ </main>
157
+
158
+
159
+
160
+ <footer id="validator-badges" role="contentinfo">
161
+ <p><a href="https://validator.w3.org/check/referer">Validate</a>
162
+ <p>Generated by <a href="https://ruby.github.io/rdoc/">RDoc</a> 6.3.0.
163
+ <p>Based on <a href="http://deveiate.org/projects/Darkfish-RDoc/">Darkfish</a> by <a href="http://deveiate.org">Michael Granger</a>.
164
+ </footer>
165
+
data/docs/LICENSE_txt.html ADDED
@@ -0,0 +1,96 @@
1
+ <!DOCTYPE html>
2
+
3
+ <html>
4
+ <head>
5
+ <meta charset="UTF-8">
6
+
7
+ <title>LICENSE - RDoc Documentation</title>
8
+
9
+ <script type="text/javascript">
10
+ var rdoc_rel_prefix = "./";
11
+ var index_rel_prefix = "./";
12
+ </script>
13
+
14
+ <script src="./js/navigation.js" defer></script>
15
+ <script src="./js/search.js" defer></script>
16
+ <script src="./js/search_index.js" defer></script>
17
+ <script src="./js/searcher.js" defer></script>
18
+ <script src="./js/darkfish.js" defer></script>
19
+
20
+ <link href="./css/fonts.css" rel="stylesheet">
21
+ <link href="./css/rdoc.css" rel="stylesheet">
22
+
23
+
24
+ <body id="top" role="document" class="file">
25
+ <nav role="navigation">
26
+ <div id="project-navigation">
27
+ <div id="home-section" role="region" title="Quick navigation" class="nav-section">
28
+ <h2>
29
+ <a href="./index.html" rel="home">Home</a>
30
+ </h2>
31
+
32
+ <div id="table-of-contents-navigation">
33
+ <a href="./table_of_contents.html#pages">Pages</a>
34
+ <a href="./table_of_contents.html#classes">Classes</a>
35
+ <a href="./table_of_contents.html#methods">Methods</a>
36
+ </div>
37
+ </div>
38
+
39
+ <div id="search-section" role="search" class="project-section initially-hidden">
40
+ <form action="#" method="get" accept-charset="utf-8">
41
+ <div id="search-field-wrapper">
42
+ <input id="search-field" role="combobox" aria-label="Search"
43
+ aria-autocomplete="list" aria-controls="search-results"
44
+ type="text" name="search" placeholder="Search" spellcheck="false"
45
+ title="Type to search, Up and Down to navigate, Enter to load">
46
+ </div>
47
+
48
+ <ul id="search-results" aria-label="Search Results"
49
+ aria-busy="false" aria-expanded="false"
50
+ aria-atomic="false" class="initially-hidden"></ul>
51
+ </form>
52
+ </div>
53
+
54
+ </div>
55
+
56
+
57
+
58
+ <div id="project-metadata">
59
+
60
+ <div id="fileindex-section" class="nav-section">
61
+ <h3>Pages</h3>
62
+
63
+ <ul class="link-list">
64
+ <li><a href="./CODE_OF_CONDUCT_md.html">CODE_OF_CONDUCT</a>
65
+ <li><a href="./CODING_GUIDELINES_md.html">CODING_GUIDELINES</a>
66
+ <li><a href="./CONTRIBUTING_md.html">CONTRIBUTING</a>
67
+ <li><a href="./LICENSE_txt.html">LICENSE</a>
68
+ <li><a href="./README_md.html">README</a>
69
+ </ul>
70
+ </div>
71
+
72
+ </div>
73
+ </nav>
74
+
75
+ <main role="main" aria-label="Page LICENSE.txt">
76
+
77
+ <p>The MIT License (MIT)</p>
78
+
79
+ <p>Copyright © 2021 Mercado Pago</p>
80
+
81
+ <p>Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p>
82
+
83
+ <p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>
84
+
85
+ <p>THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.</p>
86
+
87
+ </main>
88
+
89
+
90
+
91
+ <footer id="validator-badges" role="contentinfo">
92
+ <p><a href="https://validator.w3.org/check/referer">Validate</a>
93
+ <p>Generated by <a href="https://ruby.github.io/rdoc/">RDoc</a> 6.3.0.
94
+ <p>Based on <a href="http://deveiate.org/projects/Darkfish-RDoc/">Darkfish</a> by <a href="http://deveiate.org">Michael Granger</a>.
95
+ </footer>
96
+