You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you have inline options set in the Service and a vue config file, then inline options will be completely ignored. That is inconvenient if you want to programmatically set options but also allow the user to override these.
For example the NX Plugin for Vue.
They are setting inline options programmatically when building the application. But if I for example want to set the publicPath using a vue config file, then the normal build options are not used anymore.
What does the proposed API look like?
Is it not possible to just extend the inline options in the Service.js file? I have not looked at other classes but I do not see an usage for inline options if it is completely ignored if any other config exists.
What problem does this feature solve?
Currently if you have inline options set in the Service and a vue config file, then inline options will be completely ignored. That is inconvenient if you want to programmatically set options but also allow the user to override these.
For example the NX Plugin for Vue.
They are setting inline options programmatically when building the application. But if I for example want to set the publicPath using a vue config file, then the normal build options are not used anymore.
What does the proposed API look like?
Is it not possible to just extend the inline options in the Service.js file? I have not looked at other classes but I do not see an usage for inline options if it is completely ignored if any other config exists.
The text was updated successfully, but these errors were encountered: