First of all, before using a framework, you must read the relevant documents completely, because the common functions will be encapsulated in the framework, and it will be more in line with public requirements. On the ui design diagram, it may not be very good to realize the interaction given in a certain function design diagram, but there are better components in the framework that can be realized, but because I am not familiar with the framework without reading the document, I don’t know that it can be used . In this way, you can discuss with the product manager whether you can use the solution in the framework, the experience is better, etc., which not only simplifies the work, but also improves the experience.
So look at the documentation, it's really important.
1.Select
In iview-ui, the on-change event of the select component to obtain the selection result can not get much, and there may not be the data we want. For example: If I want to get which number is selected, I need to loop this object to see which key-value pair is equal to the return result of on-change.
For this, native vue events can be considered, and all relevant information can be obtained when clicking option.
2. There is only one second-level menu, and the first-level menu does not display the problem
① It is stated in the document that you can add showAlways to the relevant route
②Modify the relevant code, in main/components/side-menu/mixin line12, modify it to
It is also achievable.
3. Page routing cache problem
At the beginning of the routers.js file, it is said that the page name needs to be set, but the name in the page cannot use the middle line
4. Permission access
The access option under meta in the routing page is used to configure directory access rights. If the default page is not set, it can be accessed by everyone. After setting, at least one item in the meta.access array needs to exist in the total access list.
5. Time and date selection verification problem
Because the result returned by selecting the range is an array, which is different from the returned result type of only selecting time, array validation is required. And when binding to DatePicker, v-model cannot be used, and :value must be used.
6. Package white screen
In src/router/index, the mode is changed to 'hash';
vue.config.js file:
