You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -294,7 +294,7 @@ Core developers only:
294
294
295
295
#### 4.2 Dynamic (Vue.js) custom component naming
296
296
297
-
Formerly, custom components behaved differently than core components. `Components::Some::Component` was translated to a Vue.js componente named `custom-some-component`, in order to match their (now changed) dsl method name `custom_some_component`
297
+
Formerly, custom components behaved differently than core components. `Components::Some::Component` was translated to a Vue.js component named `custom-some-component`, in order to match their (now changed) dsl method name `custom_some_component`
298
298
299
299
This behavior changes in `1.0.0`:
300
300
@@ -349,7 +349,7 @@ Please note that the `components` block is still supported, but will be removed
349
349
350
350
**Migration Todos:**
351
351
352
-
-[ ] To be on the safe side, remove all the `components {}` wrapping blocks in your apps&pages
352
+
-[ ] To be on the safe side, remove all the `components {}` wrapping blocks in your apps and pages
353
353
354
354
355
355
#### 6. Partials are now normal method calls and don't need a block
@@ -418,7 +418,7 @@ We changed the naming to be more expressive and in order to align with the exist
418
418
419
419
**Migration Todos:**
420
420
421
-
-[ ] On an app layout, you should now use `yield_page` instead of `page_comtent`
421
+
-[ ] On an app layout, you should now use `yield_page` instead of `page_component`
422
422
423
423
#### 9. Wrapping DOM structure of pages has changed
424
424
@@ -482,7 +482,7 @@ which will render:
482
482
</span>
483
483
</div>
484
484
<divclass="matestack-page-wrapper">
485
-
<div><!--this div is necessary for conditonal switch to async template via v-if -->
485
+
<div><!--this div is necessary for conditional switch to async template via v-if -->
486
486
<divclass="matestack-page-root">
487
487
your page markup
488
488
</div>
@@ -503,7 +503,7 @@ and during async page request triggered via transition:
503
503
</span>
504
504
</div>
505
505
<divclass="matestack-page-wrapper loading">
506
-
<div><!--this div is necessary for conditonal switch to async template via v-if -->
506
+
<div><!--this div is necessary for conditional switch to async template via v-if -->
507
507
<divclass="matestack-page-root">
508
508
your page markup
509
509
</div>
@@ -527,7 +527,7 @@ end
527
527
528
528
**Migration Todos:**
529
529
530
-
-[ ] Please add an unique ID to each `async` component usage, even if matestack is currntly autogeneratin an ID if not applied. This will be removed in future releases
530
+
-[ ] Please add an unique ID to each `async` component usage, even if matestack is currently auto-generating an ID if not applied. This will be removed in future releases
531
531
532
532
#### 12. New `toggle` component is replacing `async` shown_on, hide_on, hide_after...
533
533
@@ -830,10 +830,10 @@ The Absolute Component has been removed and can no longer be used.
830
830
XSS/Script injection vulnerablilty fixed in 0.7.4
831
831
832
832
* matestack-ui-core was vulnerable to XSS/Script injection
833
-
* matestack-ui-core did not excape strings by default and did not cover this in the docs
833
+
* matestack-ui-core did not escape strings by default and did not cover this in the docs
834
834
* matestack-ui-core should have escaped strings by default in order to prevent XSS/Script injection vulnerability
835
835
* 0.7.4 fixes that by performing string escaping by default now
836
-
* a new component `unescaped` (like `plain` before) allows to render unsecaped strings, but forces the developer to explicitly make a concious decision about that
836
+
* a new component `unescaped` (like `plain` before) allows to render unescaped strings, but forces the developer to explicitly make a concious decision about that
0 commit comments