@rebilly/framepay-vue 7.0.1 → 7.0.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1 +1,6 @@
1
- ## [7.0.1](https://github.com/Rebilly/rebilly/compare/framepay-vue-v7.0.0...framepay-vue-v7.0.1) (2024-11-14)
1
+ ## [7.0.2](https://github.com/Rebilly/rebilly/compare/framepay-vue-v7.0.1...framepay-vue-v7.0.2) (2024-11-14)
2
+
3
+
4
+ ### Bug Fixes
5
+
6
+ * **libs: framepay-vue:** Fix broken links on README.md ([#8590](https://github.com/Rebilly/rebilly/issues/8590)) ([26e6bf3](https://github.com/Rebilly/rebilly/commit/26e6bf3b2dc11b034c1a97261005fcb10b2b28e4))
package/README.md CHANGED
@@ -90,7 +90,7 @@ app.use(FramePay);
90
90
 
91
91
  Initialization can be done at startup, or directly on a payment component. To initialize `FramePay` you will need a publishable key from [Rebilly](https://app.rebilly.com/api-keys/add). We recommend starting with a sandbox key.
92
92
 
93
- See here for all initialization options: https://rebilly.github.io/framepay-docs/reference/rebilly.html#rebilly-initialize
93
+ See here for all initialization options: https://www.rebilly.com/docs/dev-docs/framepay-configuration-reference
94
94
 
95
95
  #### At startup
96
96
 
@@ -208,9 +208,9 @@ Any DOM attributes you attach to `RebillyForm` will automatically be passed to t
208
208
 
209
209
  `@token-ready` will expose the token object, if a Google/Apple Pay element was mounted in the form.
210
210
 
211
- See here for all arguments to `extraData`: https://rebilly.github.io/framepay-docs/reference/rebilly.html#extra-data.
211
+ See here for all arguments to `extraData`: https://www.rebilly.com/docs/dev-docs/framepay-global-reference#extra-data.
212
212
 
213
- See here for list of `data-rebilly` types: https://rebilly.github.io/framepay-docs/reference/rebilly.html#data-rebilly-fields.
213
+ See here for list of `data-rebilly` types: https://www.rebilly.com/docs/dev-docs/form-setup.
214
214
 
215
215
 
216
216
  #### With rebilly-form and custom submit logic
@@ -370,7 +370,7 @@ As covered above, `rebilly-form` emits `error` and `submit` events.
370
370
 
371
371
  Payment method components emit the following events: `on`, `ready`, `focus` and `change`.
372
372
 
373
- See details: https://rebilly.github.io/framepay-docs/reference/element.html#element-on
373
+ See details: https://www.rebilly.com/docs/dev-docs/element
374
374
 
375
375
  ### Validation
376
376
 
@@ -394,7 +394,7 @@ See details: https://rebilly.github.io/framepay-docs/reference/element.html#elem
394
394
  </script>
395
395
  ```
396
396
 
397
- See details: https://rebilly.github.io/framepay-docs/reference/element.html#element-on
397
+ See details: https://www.rebilly.com/docs/dev-docs/element
398
398
 
399
399
  ### Element IDs
400
400
 
@@ -418,7 +418,7 @@ Again, you don't need to use `createToken` at all if you choose to use the `Rebi
418
418
 
419
419
  As mentioned above, Framepay will expose the `Framepay` object in the global namespace after it has loaded. We recommend that you never call the `Framepay` object directly, as `framepay-vue` is designed to either expose or abstract away all the methods you need to use Framepay.
420
420
 
421
- For more information about the `Framepay` object, see: https://www.rebilly.com/docs/dev-docs/framepay-global-reference/
421
+ For more information about the `Framepay` object, see: https://www.rebilly.com/docs/dev-docs/framepay-global-reference
422
422
 
423
423
  ### Components
424
424
 
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@rebilly/framepay-vue",
3
3
  "type": "module",
4
- "version": "7.0.1",
4
+ "version": "7.0.2",
5
5
  "description": "Official Vue wrapper for Rebilly FramePay",
6
6
  "author": "Rebilly",
7
7
  "repository": {