Skip to content
#

boilerplate

Here are 7,194 public repositories matching this topic...

akhileshacc
akhileshacc commented Dec 3, 2019

First, I am not sure how to exactly add Material UI support.
I added by doing this in client.js

<App context={context} insertCss={insertCss}>
        <MuiThemeProvider>
          <CssBaseline />
          {route.component}
        </MuiThemeProvider>
      </App>

Please tell whats the right way to integrate material UI.
Material UI applies styles well when server starts. But at

markerikson
markerikson commented Nov 18, 2019

Hi, I'm a Redux maintainer. I'd like to offer a couple suggestions.

Problem

The current Redux example implementation shows use of reducers with "hand-written" immutable update logic, and has a somewhat complex store configuration. In addition, the project currently uses a "folder-by-type" folder structure.

Proposed Solution

The project should switch to using the official [Redux

websmallrabbit
websmallrabbit commented Oct 12, 2019

I set

{
        test: /\.svg$/,
        loader: 'svg-sprite-loader',
        include: [resolve('./src/renderer/icons')],
        exclude: [resolve('./src/renderer/icons')],
        options: {
          symbolId: 'icon-[name]'
        }
      },
      {
        test: /\.(png|jpe?g|gif|svg)(\?.*)?$/,
        loader: 'url-loader',
        exclude: [resolve('./src/renderer/ic
tayfunyasar
tayfunyasar commented Dec 3, 2019

ERROR:

12-03 13:42:38.396 18257-18276/? E/ReactNativeJS: TypeError: undefined is not an object (evaluating 'console.tron.log')
12-03 13:42:38.436 18257-18277/? E/AndroidRuntime: FATAL EXCEPTION: mqt_native_modules
    Process: com.myapp, PID: 18257
    com.facebook.react.common.JavascriptException: TypeError: undefined is not an object (evaluating 'console.tron.log'), stack:
    <unknown
markerikson
markerikson commented Nov 18, 2019

Hi, I'm a Redux maintainer. I'd like to offer a couple suggestions.

Is your feature request related to a problem? Please describe.

The current Redux example implementation shows use of reducers with "hand-written" immutable update logic, and has a somewhat complex store configuration. In addition, the project currently uses a "folder-by-type" folder structure.

**Describe the solutio

marceloavf
marceloavf commented Oct 21, 2019

I saw that there is an extension for eslint to automatically organize imports, allowing them to be more readable, It should be nice to have some in this project.

// 3rd party packages
import Vue from 'vue'

// Stores
import Store from '@Store'

// reusable components
import Button from '@components/Button'

// utility functions
import { add, subtract } from '@utils/calculate'

wsanchez
wsanchez commented Nov 12, 2019

I'm getting a new handy error from mypy:

src/ims/application/_main.py:74:2: error: cmp is deprecated, use eq and order  [misc]

In order to make sure I'm using those correctly, I went to attrs.org and looked for some documentation on these new options, but I see no mention of either of the eq or order options, except for some mentions of eq in the section on hashing

mikro45
mikro45 commented Nov 8, 2019

To show the tab to the user, tab requires 'show' class to actually show, otherwise it stays hidden.

That doesn't happen on the page load on the first tab, so the first tab will be visible only after you click on the other one and then back on the first, when it finally gets the 'show' class.

You can see it on the modularcode page at "Pill tabs" section.
https://modularcode.io/modular-admin-

mininternet
mininternet commented Feb 9, 2018

@diegohaz - i noticed a couple of minor spelling errors on the main site:

Basic stack
It includes everything necessary to build a tipical web app with focus on productivity and developer experience.
Learn more about the recomended workflow

Should be typical, and recommended.

Just an FYI.

Thanks!

aman3991
aman3991 commented Feb 24, 2019

Despite of a great a project, it difficult to flow through the project source code. It would be great if a system architecture or a workflow diagram could be provide to acknowledge the re-usability of this project.

Enalmada
Enalmada commented Sep 9, 2018

At the bottom of server.js, there are some paths like manifest.html, manifest.appcache, etc that don't resolve. Perhaps they were constructs from older version of next.js? I am totally new to what they might be so if those are there for a reason could you comment why/what we should be doing to benefit from them?

server.get('/sw.js', (req, res) => app.serveStatic(req, res, path.resolve('./.

bug

Improve this page

Add a description, image, and links to the boilerplate topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the boilerplate topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.