Home > front end >  Vue cli js plug-in to distributed development to realize the increasing function of the plugin
Vue cli js plug-in to distributed development to realize the increasing function of the plugin

Time:12-08

at present, the company's new project, demand more exotic, demand goes like this:
project to use vue - cli to produce packaging, packaging has completed less than different clients need to deploy in order to realize the different data access on the server
The problem here: if the customer need A custom function, but customers don't need to B, as webpack packaging cannot directly to modify, but if the local modification to pack cover the customer A server, the server if the next client B problems to modify (A customer need more customers don't need the function of B)
So someone will ask, why not go to do two sets of code, which need to change which code to repackage, personalized each other, the question again:
this project began a bug, you need to change all the client source code, the client should have dozens, hundreds, can store dozens of hundreds of local code is no problem, but this one change the amount of work is much like the development state of the original??
So excuse me: can have any good plan implementation:
solve bug: to develop a set of code, with all the client's new js file
Increasing individuation function: a js plug-in upload/cover to the corresponding client server can
Increasing unity function: a js plug-ins, upload/coverage to drink on the client server can

CodePudding user response:

Do all the places need to modify the configuration files

CodePudding user response:

The building Lord you said not is the operation mode of the Git,,
First built a Dev branch code is AB needs is the public part of

Then on the basis of common code to build two new branch Dev_A and Dev_B were used to develop AB client code,

CodePudding user response:

refer to the second floor bath _ fire phoenix reply:
the building Lord you said not is the operation mode of the Git,,
First built a Dev branch code is AB needs is the public part of

Then on the basis of common code to build two new branch Dev_A and Dev_B were used to develop AB client code,

Now have a question, the code what's written general pattern: I know, more headaches is below and the problem, move to the common components? I am using the vue framework

CodePudding user response:

reference 3 floor smoke village four or five home a reply:
Quote: refer to the second floor bath _ fire phoenix reply:
the building Lord you said not is the operation mode of the Git,,
First built a Dev branch code is AB needs is the public part of

Then on the basis of common code to build two new branch Dev_A and Dev_B were used to develop AB client code,

Now have a question, the code what's written general pattern: I know, more headaches is below and the problem, move to the common components? I am using the vue framework

CodePudding user response:

With the framework it doesn't matter,
Two customers have the same function you modify the public part is Dev branch
if changed the public part and test passed remember the code use git merge merged into Dev_A Dev_B two branches
Or two branches of the custom after increasing demand can lack of this part of the function

AB respective demand change before you switch to the corresponding branch,

CodePudding user response:

refer to fifth floor bath _ fire phoenix reply:
with framework it doesn't matter,
Two customers have the same function you modify the public part is Dev branch
if changed the public part and test passed remember the code use git merge merged into Dev_A Dev_B two branches
Or two branches of the custom after increasing demand can lack of this part of the function

AB respective demand change before you switch to the corresponding branch,
that how to avoid the customer personalization amended public some influence to the main branch of the component?

CodePudding user response:

Didn't understand what you mean
  • Related