The idea of building vuejs bullet layer?

clipboard.png

"" "" ""

clipboard.png

w()w


htmlvuejswillData:1,2,3

clipboard.png

May.10,2021

Cross-domain has nothing to do with how we design the front end. It mainly depends on whether the background gives you cross-domain, and just let the little brother in the background give you cross-domain. During the development phase, you can set up a proxy in the configuration file to avoid cross-domain. See here . To put it bluntly, cross-domain is a secure prevention mechanism, which belongs to the communication layer, not the presentation layer.


in fact, it is not difficult, if you just do a pop-up box component, it should be like this, this component designs the mask layer and display panel, the content of the display board uses slot for external injection, of course, if it is dedicated, you can write the specific content directly.

parameters involved: whether the pop-up box is displayed as a v-model open to the public. In addition to this, if it is about the close button or the above click, you need to trigger the click event. If you need to do something before the pop-up box is closed, you need to trigger before-close and after-close events. If the form component is involved, whether the pop-up box needs to be new each time requires destory-on-close

.

as for what to do in the end, it is to add what is needed. The component is nothing more than communicating with the outside world. The component only does what the component does and cannot be blended, and it is difficult to maintain and expand later.

in the case of cross-domain problems, webpack-dev-server can be used for proxy configuration in the development phase, and server configuration is required online to allow cross-domain configuration.


there are two ways to implement the spring layer

  1. write the code of the pop-up layer to the current page, which is controlled by the current page and directly manipulates the variables of the current page. If the pop-up layer is a common component, you can insert it with slot , as follows:
const popup = PopupManager.open(....);
popup.on('change', (key, value) => this[key] = value);

the cross-domain error reported by the query interface should have nothing to do with the pop layer. It is recommended to check other codes.

Menu