Step 10.3: Use module replacement to achieve component overrides
This is the same system as the customisations override, however deliberately using a different JSON file to avoid conflicts. Forks would be expected to use the customisations file, not the components file, to override/add components.
This commit is contained in:
parent
5459c1eb96
commit
5b592eca4f
5 changed files with 27 additions and 18 deletions
|
@ -44,6 +44,4 @@ const VectorAuthFooter = () => {
|
|||
);
|
||||
};
|
||||
|
||||
VectorAuthFooter.replaces = 'AuthFooter';
|
||||
|
||||
export default VectorAuthFooter;
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue