-
Notifications
You must be signed in to change notification settings - Fork 17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I run docker-compose up --build
I get the following error:
ERROR in ./styleguide/src/system/components/data-input/Select/style.scss?vue&type=style&index=0&lang=scss& (./node_modules/css-loader??ref--6-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--6-oneOf-1-2!./node_modules/sass-loader/lib/loader.js??ref--6-oneOf-1-3!./node_modules/sass-resources-loader/lib/loader.js??ref--6-oneOf-1-4!./styleguide/src/system/components/data-input/Select/style.scss?vue&type=style&index=0&lang=scss&)
Module build failed (from ./node_modules/sass-loader/lib/loader.js):
}
^
Undefined variable: "$z-index-dropdown".
in /nitro-web/styleguide/src/system/components/data-input/Select/style.scss (line 129, column 12)
@ ./styleguide/src/system/components/data-input/Select/style.scss?vue&type=style&index=0&lang=scss& (./node_modules/vue-style-loader!./node_modules/css-loader??ref--6-oneOf-1-1!./node_modules/vue-loader/lib/loaders/stylePostLoader.js!./node_modules/postcss-loader/src??ref--6-oneOf-1-2!./node_modules/sass-loader/lib/loader.js??ref--6-oneOf-1-3!./node_modules/sass-resources-loader/lib/loader.js??ref--6-oneOf-1-4!./styleguide/src/system/components/data-input/Select/style.scss?vue&type=style&index=0&lang=scss&) 4:14-452
@ ./styleguide/src/system/components/data-input/Select/style.scss?vue&type=style&index=0&lang=scss&
@ ./styleguide/src/system/components/data-input/Select/Select.vue
@ ./styleguide/src/system/components sync \.vue$
@ ./styleguide/src/system/components/index.js
@ ./styleguide/src/system/index.js
@ ./plugins/design-system.js
@ ./.nuxt/index.js
@ ./.nuxt/client.js
@ multi ./.nuxt/client.js
Also, please add component tests to this PR. Component tests should be easy to setup as we did it once already for our previous WebApp.
Then the docker pipeline is not working correctly. Locally and on Travis it works correctly. @roschaefer for that you are currently the expert. Any suggestions? |
My suggestion for you is to run |
My other suggestion is to run |
As I do not use pc as my driver I would be way more then 600€. So I can’t afford it at the moment. And as docker is frying my seven year old machine. So I will use the powers of my native system for now 😉 |
@appinteractive I see the above bug on |
I am finally able to build the docker container but just don't know what I have changed. I believe, we have some .gitignored folders in the styleguide that can cause trouble when you switch back and forth branches. |
I merged in #84 consider to merge that PR before reviewing this PR. |
@visualjerk could you help us out on this PR? I'm trying to get rid of this error: ``` Unknown custom element: <ds-table> - did you register the component correctly? For recursive components, make sure to provide the "name" option. ``` How do we tell @vue/test-utils to stub globally registered components? Second, I don't understand why the resulting html() of the categories components looks so odd: ``` <h1 class="ds-heading ds-heading-h1" space="small" categories="[object Object],[object Object],[object Object],[object Object],[object Object]"> <h3 class="ds-card"><!----> <!----> <!----> <div class="ds-card-content"> Themen / Kategorien </div> <!----></h3> <ds-table data="" fields="icon,name,postCount" condensed=""></ds-table></h1> ``` Why on earth does the categories array end up in the `categories` property of `ds-heading` component? @visualjerk and @appinteractive have a look, please 😘
…/hc-prototype-ui into admin-tags-and-categories
@@ -19,6 +19,7 @@ | |||
style="float: right" | |||
> | |||
<a | |||
class="avatar-menu" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@appinteractive do we use some sort of fancy CSS naming like BEM?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah kinda, as you can see we prefix the styles with the component name. But not actually in the ugly BEM style.
@appinteractive and I decided to test the page with a fullstack test. It makes more sense for pages who request data from the backend.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@appinteractive good to merge
@roschaefer the wrong backend branch is checked out! That’s why it failes. |
@appinteractive ha! The PR check fails because it's on |
@appinteractive maybe we can start with a workflow to merge the backend first and then run the full stack tests again? |
@appinteractive green! Wohoo |
…@babel/node-7.2.2 Bump @babel/node from 7.2.0 to 7.2.2
Use with Human-Connection/Nitro-Backend#62
Added Tags and Categories to the Admin area