Browse Source

Merge dev

up-style-manager
Artur Arseniev 4 years ago
parent
commit
e0238fec77
  1. 2
      dist/css/grapes.min.css
  2. 2
      docs/modules/Blocks.md
  3. 2
      src/styles/scss/_gjs_devices.scss

2
dist/css/grapes.min.css

File diff suppressed because one or more lines are too long

2
docs/modules/Blocks.md

@ -135,7 +135,7 @@ Using HTML strings as `content` is not wrong, in some cases you don't need the f
```
In such a case, all rendered elements will be converted to the best suited default component (eg. `.el-Y` elements will be treated like `text` components). The user will be able to style and drag them with no particular restrictions.
Thanks to Components' [isComponet](http://localhost:8081/docs/modules/Components.html#iscomponent) feature (executed post parsing), you're still able to bind your rendered elements to components and enforce an extra logic. Here an example how you would enforce all `.el-Y` elements to be placed only inside `.el-X` one, without touching any part of the original HTML used in the `content`.
Thanks to Components' [isComponet](Components.html#iscomponent) feature (executed post parsing), you're still able to bind your rendered elements to components and enforce an extra logic. Here an example how you would enforce all `.el-Y` elements to be placed only inside `.el-X` one, without touching any part of the original HTML used in the `content`.
```js
// Your component

2
src/styles/scss/_gjs_devices.scss

@ -1,7 +1,7 @@
.#{$app-prefix}devices-c {
display: flex;
align-items: center;
padding: 3px;
padding: 2px 3px 3px 3px;
.#{$app-prefix}device-label {
flex-grow: 2;

Loading…
Cancel
Save