在线观看不卡亚洲电影_亚洲妓女99综合网_91青青青亚洲娱乐在线观看_日韩无码高清综合久久

遇到相同問(wèn)題了，重新加載之后能運(yùn)行，可是斷點(diǎn)什么的都不起作用

為毛不能傳？
edit({item, idx})
edit(item, idx)
應(yīng)該都行啊

我找到答案了，是我的錯(cuò)。我取出的時(shí)候應(yīng)該：

this.$route.params.is_used這樣取出.

因?yàn)槠渌麢C(jī)器訪問(wèn)localhost 相當(dāng)于訪問(wèn)它自己，如果你需要讓PC2 訪問(wèn)PC1 的服務(wù)，請(qǐng)直接使用ip地址；

TIPS：在計(jì)算機(jī)網(wǎng)絡(luò)中，localhost（意為“本地主機(jī)”，指“這臺(tái)計(jì)算機(jī)”）是給回路網(wǎng)絡(luò)接口（loopback）的一個(gè)標(biāo)準(zhǔn)主機(jī)名，相對(duì)應(yīng)的IP地址為127.0.0.1（IPv4）和[::1]（IPv6）。

.opacity(@number){
  /* older safari/Chrome browsers */
  -webkit-opacity: @number/100;
  /* Netscape and Older than Firefox 0.9 */
  -moz-opacity: @number/100;
  /* Safari 1.x (pre WebKit!) 老式khtml內(nèi)核的Safari瀏覽器*/
  -khtml-opacity: @number/100;
  /* IE9 + etc...modern browsers */
  opacity: @number/100;
  /* IE 4-9 */
  filter:alpha(opacity=@number);
  /*This works in IE 8 & 9 too*/
  -ms-filter:progid:DXImageTransform.Microsoft.Alpha(Opacity=@number);
  /*IE4-IE9*/
  filter:progid:DXImageTransform.Microsoft.Alpha(Opacity=@number);

}

spring mvc上傳文件的時(shí)候，你需要在spring mvc配置文件中配置org.springframework.web.multipart.commons.CommonsMultipartResolver文件上傳解析器。

1：當(dāng)一個(gè)請(qǐng)求過(guò)來(lái)的時(shí)候，會(huì)調(diào)用DispatcherServlet類中的doDispatch(HttpServletRequest, HttpServletResponse)方法。

doDispatch方法體

protected void doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception {
        HttpServletRequest processedRequest = request;
        HandlerExecutionChain mappedHandler = null;
        boolean multipartRequestParsed = false;

        WebAsyncManager asyncManager = WebAsyncUtils.getAsyncManager(request);

        try {
            ModelAndView mv = null;
            Exception dispatchException = null;

            try {
                processedRequest = checkMultipart(request);
                multipartRequestParsed = processedRequest != request;

                // Determine handler for the current request.
                mappedHandler = getHandler(processedRequest, false);
                if (mappedHandler == null || mappedHandler.getHandler() == null) {
                    noHandlerFound(processedRequest, response);
                    return;
                }

                // Determine handler adapter for the current request.
                HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler());

                // Process last-modified header, if supported by the handler.
                String method = request.getMethod();
                boolean isGet = "GET".equals(method);
                if (isGet || "HEAD".equals(method)) {
                    long lastModified = ha.getLastModified(request, mappedHandler.getHandler());
                    if (logger.isDebugEnabled()) {
                        String requestUri = urlPathHelper.getRequestUri(request);
                        logger.debug("Last-Modified value for [" + requestUri + "] is: " + lastModified);
                    }
                    if (new ServletWebRequest(request, response).checkNotModified(lastModified) && isGet) {
                        return;
                    }
                }

                if (!mappedHandler.applyPreHandle(processedRequest, response)) {
                    return;
                }

                try {
                    // Actually invoke the handler.
                    mv = ha.handle(processedRequest, response, mappedHandler.getHandler());
                }
                finally {
                    if (asyncManager.isConcurrentHandlingStarted()) {
                        return;
                    }
                }

                applyDefaultViewName(request, mv);
                mappedHandler.applyPostHandle(processedRequest, response, mv);
            }
            catch (Exception ex) {
                dispatchException = ex;
            }
            processDispatchResult(processedRequest, response, mappedHandler, mv, dispatchException);
        }
        catch (Exception ex) {
            triggerAfterCompletion(processedRequest, response, mappedHandler, ex);
        }
        catch (Error err) {
            triggerAfterCompletionWithError(processedRequest, response, mappedHandler, err);
        }
        finally {
            if (asyncManager.isConcurrentHandlingStarted()) {
                // Instead of postHandle and afterCompletion
                mappedHandler.applyAfterConcurrentHandlingStarted(processedRequest, response);
                return;
            }
            // Clean up any resources used by a multipart request.
            if (multipartRequestParsed) {
                cleanupMultipart(processedRequest);
            }
        }
    }

2：在doDispatch方法體中調(diào)用checkMultipart(request)方法判斷是否是文件上傳的請(qǐng)求，判斷是根據(jù)Content-type來(lái)的，如果是文件上傳的請(qǐng)求，在checkMultipart(request)方法中就會(huì)調(diào)用在CommonsMultipartResolver中的方法進(jìn)行文件解析(實(shí)際是調(diào)用apache commons-fileupload的文件長(zhǎng)傳插件)，解析完成后，其實(shí)文件已經(jīng)上傳到服務(wù)器本地磁盤了，請(qǐng)看下面的代碼片段。

protected HttpServletRequest checkMultipart(HttpServletRequest request) throws MultipartException {
        if (this.multipartResolver != null && this.multipartResolver.isMultipart(request)) {
            if (request instanceof MultipartHttpServletRequest) {
                logger.debug("Request is already a MultipartHttpServletRequest - if not in a forward, " +
                        "this typically results from an additional MultipartFilter in web.xml");
            }
            else {
                return this.multipartResolver.resolveMultipart(request);
            }
        }
        // If not returned before: return original request.
        return request;
    }

在checkMultipart方法體中調(diào)用了CommonsMultipartResolver類的resolveMultipart方法去解析文件，該方法返回的是MultipartHttpServletRequest對(duì)象，該對(duì)象中存有已經(jīng)上傳的服務(wù)器本地的文件對(duì)象。

3:獲取具體處理器的方法（mv = ha.handle(processedRequest, response, mappedHandler.getHandler()) 這行代碼）。
如果是文件上傳的話，processedRequest是上面的checkMultipart方法返回的對(duì)象。

實(shí)際調(diào)用的org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter類的handle方法，該方法中獲取實(shí)際被調(diào)用的方法參數(shù)上有哪些注解，然后根據(jù)注解的一些配置，從processedRequest獲取對(duì)應(yīng)的值。

比如你上面的testUpload（）方法。在AnnotationMethodHandlerAdapter的handle（）的方法中會(huì)獲取testUpload（）的方法參數(shù)有@RequestParam這個(gè)注解，然后解析這個(gè)注解，從processedRequest請(qǐng)求中獲取到desc的值，獲取到名為file的文件，最后調(diào)用testUploaad()方法。具體是怎么解析的可以看看org.springframework.web.bind.annotation.support.HandlerMethodInvoker.resolveHandlerArguments(Method, Object, NativeWebRequest, ExtendedModelMap)這個(gè)方法體。

推薦使用vscode，簡(jiǎn)單、好用

找到問(wèn)題了,使用antd創(chuàng)建的項(xiàng)目生成的是webpack3.x,但是生成的css-module要求是webpack4.x,太坑了

第一段代碼，所有的i都指向foo中定義的i，其中f1/f2/foo()()的i各自獨(dú)立；

第二段代碼，this始終指向window，因此全程都在操作同一個(gè)i，即全局定義的i，初始值100

當(dāng)自己應(yīng)用訪問(wèn)第三方API 不應(yīng)該由前端來(lái)弄吧，基本都是由后端來(lái)處理。
跨域是瀏覽器的限制，小水管也只能這么用了

https://doc.webpack-china.org...
webpack v4 已經(jīng)移除了這個(gè)plugin，替代的是:
https://doc.webpack-china.org...

store被修改了？
給運(yùn)行正常的代碼:
store.js

import {createStore, applyMiddleware, compose} from 'redux';
import thunkMiddleware from 'redux-thunk';
import createLogger from 'redux-logger';
import YourReducer from '../reducers/YourReducer.js'; //import your reducer
let createStoreWithMiddleware = null;

if(process.env.NODE_ENV === 'production') {
    createStoreWithMiddleware = compose(applyMiddleware(
        thunkMiddleware
    ))(createStore);
} else {
    createStoreWithMiddleware = compose(applyMiddleware(
        thunkMiddleware,
        createLogger()
    ), window.devToolsExtension ? window.devToolsExtension() : f => f)(createStore);
}

export default (initState) => {
    return createStoreWithMiddleware(YourReducer, initState);
}

index.js

import {Provider} from 'react-redux';
import store from './stores/store.js';
<Provider store={store()}>
//...
</Provider>

data(){
    return {
        routeName: 'A'
    }
}
watch:{
    '$route':function(to,from){
        this.routeName = to.name
    }
}

然后用routeName去判斷哪個(gè)該高亮

不用selection

    <el-table-column  width="55">
     <template slot-scope="scope">
     <el-checkbox v-model="scope.row.checked"></el-checkbox>
     </template>
    </el-table-column>

tableData3: [{
    date: '2016-05-03',
    name: '王小虎',
    address: '上海市普陀區(qū)金沙江路 1518 弄',
    checked:true
}

你這個(gè)列表本來(lái)就是循環(huán)出來(lái)的，只要點(diǎn)擊checkbox的時(shí)候把這整個(gè)列表傳值到方法里操作就行了啊，里面的字段是v-model的，會(huì)雙向綁定

拆分成兩個(gè)組件

你可以這么寫
把 var name = 'bb[0]';====> 通過(guò)正則轉(zhuǎn)換成 var test = ['bb', '0']

然后 newData = data[test[0]].test[1]

1.圖是怎么來(lái)的？

這個(gè)圖是a標(biāo)簽的父級(jí)元素ul的背景圖里的，背景圖是一張雪碧圖定位定出來(lái)的。

2.這個(gè)-9999px有什么用？我只能靠平時(shí)-9999的作用去猜測(cè)網(wǎng)易為什么在這里去做-9999

可能因?yàn)檫@個(gè)a標(biāo)簽是要被點(diǎn)擊的，而且有hover事件，所以一定要有一定的寬高，所以會(huì)變成一個(gè)block型，既然會(huì)有寬高索性內(nèi)容寫個(gè)pc，還能讓文檔更有語(yǔ)義化
-9999只是這個(gè)文字不展示，但是文字還是在的，從理論上來(lái)說(shuō)還是會(huì)被搜索引擎爬到的，也有利于seo，當(dāng)然這里有沒有這個(gè)作用，全靠猜測(cè)

tabbar的定義呢

你好，請(qǐng)問(wèn) js 是外部發(fā)送執(zhí)行的需要怎么更改呢