@epam/ai-dial-modulify-ui 0.19.0-rc.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +346 -0
- package/index.esm.d.ts +1 -0
- package/index.esm.js +10690 -0
- package/package.json +19 -0
- package/src/index.d.ts +2 -0
- package/src/lib/ComponentBuilder.d.ts +56 -0
- package/src/lib/ComponentBuilder.test.d.ts +1 -0
- package/src/lib/Inversify.d.ts +22 -0
- package/src/lib/Inversify.test.d.ts +1 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2023 EPAM Systems, Inc.
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,346 @@
|
|
|
1
|
+
# Modulify Toolkit (UI)
|
|
2
|
+
|
|
3
|
+
## Modulify-UI: Enhancing React Component Flexibility and Customization
|
|
4
|
+
|
|
5
|
+
Modulify-UI is a React library comprised of two powerful tools, **Inversify** and **ComponentBuilder**, designed to enhance component's flexibility and simplify complex customization processes.
|
|
6
|
+
|
|
7
|
+
**In short:**
|
|
8
|
+
|
|
9
|
+
- **Inversify:** decouples the implementation of components to facilitate easy swapping and ensure conflict-free customization of forked code.
|
|
10
|
+
- **ComponentBuilder:** structures component building with fine-grained control over state, styles, HTML, and more.
|
|
11
|
+
|
|
12
|
+
If you aim to manage multiple implementations of a component, streamline customizations, or structure your component logic for enhanced maintainability, Modulify-UI's toolkit provides efficient solutions to simplify your React development workflow.
|
|
13
|
+
|
|
14
|
+
### Inversify: Dynamic Component Swapping
|
|
15
|
+
|
|
16
|
+
**Key Features:**
|
|
17
|
+
|
|
18
|
+
- Register original components to facilitate future customization.
|
|
19
|
+
- Resolve registered components and bind new implementations at runtime.
|
|
20
|
+
- Seamlessly swap component implementations without modifying original source code.
|
|
21
|
+
|
|
22
|
+
**Inversify** facilitates the decoupling of component implementations from their usage. By registering the original component and subsequently binding a new implementation to it during runtime, developers gain precise control over component rendering while avoiding tight coupling and code entanglement. This is particularly useful for:
|
|
23
|
+
|
|
24
|
+
- A/B testing of different component variations.
|
|
25
|
+
- Feature toggling to enable or disable specific implementations.
|
|
26
|
+
- Adapting component's behavior based on a context (e.g., user roles, device type).
|
|
27
|
+
- Customizing components in forked codebases without creating merge conflicts.
|
|
28
|
+
|
|
29
|
+
#### Example
|
|
30
|
+
|
|
31
|
+
Imagine you have a core component `Button` in your application that is used across different features. You foresee the need to alter its behavior or appearance in the future but want to avoid directly changing the original file of the component to keep the core codebase clean.
|
|
32
|
+
|
|
33
|
+
```tsx
|
|
34
|
+
import Inversify from './path/to/Inversify';
|
|
35
|
+
|
|
36
|
+
import { FC } from 'react';
|
|
37
|
+
|
|
38
|
+
interface ButtonProps {
|
|
39
|
+
onClick: () => void;
|
|
40
|
+
variant?: 'primary' | 'secondary';
|
|
41
|
+
children: React.ReactNode;
|
|
42
|
+
}
|
|
43
|
+
|
|
44
|
+
// Wrap the Button component with Inversify.register
|
|
45
|
+
// This allows for future customizations without modifying this file
|
|
46
|
+
const Button: FC<ButtonProps> = Inversify.register('Button', ({ onClick, variant, children }) => (
|
|
47
|
+
<button onClick={onClick} className={`button ${variant}`}>
|
|
48
|
+
{children}
|
|
49
|
+
</button>
|
|
50
|
+
));
|
|
51
|
+
|
|
52
|
+
// ...later in your application code...
|
|
53
|
+
|
|
54
|
+
const resolvedButton = Inversify.resolve(Button.original);
|
|
55
|
+
|
|
56
|
+
// Conditionally bind a different implementation, e.g., for A/B testing
|
|
57
|
+
if (Math.random() > 0.5) {
|
|
58
|
+
resolvedButton.bind((originalButton) => (props) => {
|
|
59
|
+
const { variant, ...restProps } = props;
|
|
60
|
+
return <originalButton {...restProps} variant={variant === 'primary' ? 'secondary' : 'primary'} />;
|
|
61
|
+
});
|
|
62
|
+
}
|
|
63
|
+
|
|
64
|
+
// Render the button with the bound implementation
|
|
65
|
+
const renderedButton = resolvedButton.render();
|
|
66
|
+
|
|
67
|
+
const App = () => {
|
|
68
|
+
return (
|
|
69
|
+
<div>
|
|
70
|
+
<renderedButton onClick={() => console.log('Clicked!')} variant="primary">
|
|
71
|
+
Click me
|
|
72
|
+
</renderedButton>
|
|
73
|
+
</div>
|
|
74
|
+
);
|
|
75
|
+
};
|
|
76
|
+
|
|
77
|
+
export default App;
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
In this example, the `bind` method provides the original `Button` component as an argument to the factory function, allowing you to render it with modified props. This illustrates how you can effortlessly modify the behavior or appearance of a component without impacting its core implementation.
|
|
81
|
+
|
|
82
|
+
#### `Inversify.register(name: string, component: OC)`
|
|
83
|
+
|
|
84
|
+
Registers a React component, associating it with a provided name. The name is primarily used for debugging and does not affect the registration itself. Importantly, registration is done using the component's function reference, and only one original component can be registered for a given function.
|
|
85
|
+
|
|
86
|
+
```tsx
|
|
87
|
+
// Registering the original component with Inversify
|
|
88
|
+
const MyComponent = Inversify.register('MyComponent', OriginalComponent);
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
#### `Inversify.resolve(component: OC)`
|
|
92
|
+
|
|
93
|
+
Provides an interface to interact with a registered component. It returns an object with methods to:
|
|
94
|
+
|
|
95
|
+
- Access the original registered component via the `original` property.
|
|
96
|
+
- Retrieve the currently active implementation (original or bound) using `instance()`.
|
|
97
|
+
- Bind a new implementation using `bind(factory)`. This method accepts a factory function that receives the original component as an argument and should return a new component implementation. Each call to `bind` replaces the previous factory, ensuring that only one active implementation is in effect at a time.
|
|
98
|
+
- Unbind the current implementation, reverting to the original component, with `unbind()`.
|
|
99
|
+
- Render the component, potentially with the bound implementation, using `render()`.
|
|
100
|
+
|
|
101
|
+
```tsx
|
|
102
|
+
// Accessing the original component and binding a new implementation
|
|
103
|
+
const RenderedComponent = Inversify.resolve(MyComponent.original)
|
|
104
|
+
.bind((originalComponent) => (props) => (
|
|
105
|
+
// Accessing and using the original component within the factory
|
|
106
|
+
<div style={{ border: '2px solid red' }}>
|
|
107
|
+
<originalComponent {...props} />
|
|
108
|
+
</div>
|
|
109
|
+
))
|
|
110
|
+
.render();
|
|
111
|
+
|
|
112
|
+
// If you need to revert to the original component, unbind to the original
|
|
113
|
+
Inversify.resolve(MyComponent.original).unbind();
|
|
114
|
+
```
|
|
115
|
+
|
|
116
|
+
### ComponentBuilder: Structured Component Customization
|
|
117
|
+
|
|
118
|
+
**Key Features:**
|
|
119
|
+
|
|
120
|
+
- Manage state, styles, HTML structure, event handlers, and side effects in a structured manner.
|
|
121
|
+
- Chain customization methods for a fluent coding style.
|
|
122
|
+
- Target styles and classes to both the component itself and a wrapping "host" element.
|
|
123
|
+
|
|
124
|
+
**ComponentBuilder** introduces a structured pattern for building React components, promoting maintainability and simplifying complex customizations.
|
|
125
|
+
|
|
126
|
+
#### Example
|
|
127
|
+
|
|
128
|
+
```tsx
|
|
129
|
+
import ComponentBuilder from './path/to/ComponentBuilder';
|
|
130
|
+
|
|
131
|
+
import React, { FC } from 'react';
|
|
132
|
+
|
|
133
|
+
const MyComponent: FC = () => (
|
|
134
|
+
<div>
|
|
135
|
+
<span data-customize-id="my-text">Hello, world!</span>
|
|
136
|
+
</div>
|
|
137
|
+
);
|
|
138
|
+
|
|
139
|
+
const CustomizedComponent = ComponentBuilder.use(MyComponent)
|
|
140
|
+
.updateClassNames((classNames) => ({
|
|
141
|
+
// These classes will be applied to a wrapping <div>
|
|
142
|
+
host: ['custom-class', classNames.host].flat(),
|
|
143
|
+
// These classes will be applied to the <MyComponent> element
|
|
144
|
+
component: ['another-class'],
|
|
145
|
+
}))
|
|
146
|
+
.updateStyles((styles) => ({
|
|
147
|
+
host: {
|
|
148
|
+
backgroundColor: 'lightblue',
|
|
149
|
+
...styles.host,
|
|
150
|
+
'&:hover': {
|
|
151
|
+
// CSS selector targeting the host element
|
|
152
|
+
backgroundColor: 'blue',
|
|
153
|
+
},
|
|
154
|
+
},
|
|
155
|
+
component: {
|
|
156
|
+
fontSize: '2em', // Styles applied directly to the component
|
|
157
|
+
},
|
|
158
|
+
}))
|
|
159
|
+
.updateHTML({
|
|
160
|
+
'my-text': (children) => <a href="#">{children}</a>,
|
|
161
|
+
})
|
|
162
|
+
.build();
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
#### `ComponentBuilder.use(component: Component)`
|
|
166
|
+
|
|
167
|
+
Initializes a new `ComponentBuilder` instance for a given React component, enabling subsequent customization methods to be chained.
|
|
168
|
+
|
|
169
|
+
```tsx
|
|
170
|
+
const builder = ComponentBuilder.use(MyComponent);
|
|
171
|
+
```
|
|
172
|
+
|
|
173
|
+
**ComponentBuilder** provides fine-grained control over styling and class names. You can target both the component itself and a wrapping `div` element (referred to as the "host"). This is achieved using the `component` and `host` properties within the styling and class name functions.
|
|
174
|
+
|
|
175
|
+
- **Styling and Classes for the Component:** When you define styles or class names under the `component` property, they are applied directly to the root element of your component. This ensures style isolation as generated CSS class names are unique to the component.
|
|
176
|
+
|
|
177
|
+
- **Styling and Classes for the Host (Wrapper):** If you need to apply styles or classes to a wrapping `div` element, use the `host` property. This is useful for controlling the layout or appearance of the component within its parent container. In most scenarios, there's no need to add a wrapping `div` element to your component, so using the `host` property should generally be unnecessary.
|
|
178
|
+
|
|
179
|
+
#### `updateClassNames(updateFn)`
|
|
180
|
+
|
|
181
|
+
Provides a mechanism to dynamically update the CSS classes applied to a component based on its state or other factors.
|
|
182
|
+
|
|
183
|
+
```tsx
|
|
184
|
+
builder.updateClassNames((classNames, state) => ({
|
|
185
|
+
host: state.isActive ? 'active' : 'inactive', // Applied to a wrapping <div>
|
|
186
|
+
component: 'my-component', // Applied to the component itself
|
|
187
|
+
}));
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
#### `updateStyles(updateFn)`
|
|
191
|
+
|
|
192
|
+
Enables the dynamic application and modification of inline styles based on changes in component state or props. This method leverages `react-jss` under the hood, providing the flexibility to define styles for specific CSS selectors as well.
|
|
193
|
+
|
|
194
|
+
```tsx
|
|
195
|
+
builder.updateStyles((styles, state) => ({
|
|
196
|
+
host: {
|
|
197
|
+
backgroundColor: state.isActive ? 'blue' : 'gray',
|
|
198
|
+
'&:hover': {
|
|
199
|
+
// CSS selector targeting the host element
|
|
200
|
+
opacity: 0.8,
|
|
201
|
+
},
|
|
202
|
+
},
|
|
203
|
+
component: {
|
|
204
|
+
// Styles applied directly to the component
|
|
205
|
+
fontSize: '1.2em',
|
|
206
|
+
},
|
|
207
|
+
}));
|
|
208
|
+
```
|
|
209
|
+
|
|
210
|
+
#### `updateHTML(htmlContentFnOrBlocks)`
|
|
211
|
+
|
|
212
|
+
Facilitates the modification of a component's internal HTML structure, enabling the addition, removal, or alteration of elements depending on specific conditions. You can provide either a single function to modify the entire HTML structure or a map of functions to target specific elements identified by the `data-customize-id` attribute.
|
|
213
|
+
|
|
214
|
+
```tsx
|
|
215
|
+
// Modifying the entire HTML structure
|
|
216
|
+
builder.updateHTML((children, state) => (
|
|
217
|
+
<>
|
|
218
|
+
{state.showHeader && <h1>Header</h1>}
|
|
219
|
+
{children}
|
|
220
|
+
</>
|
|
221
|
+
));
|
|
222
|
+
|
|
223
|
+
// Targeting specific elements by data-customize-id
|
|
224
|
+
builder.updateHTML({
|
|
225
|
+
'my-element-id': (children) => <div className="custom-style">{children}</div>,
|
|
226
|
+
});
|
|
227
|
+
```
|
|
228
|
+
|
|
229
|
+
#### `updateHandlers(updateFn)`
|
|
230
|
+
|
|
231
|
+
Provides a way to manage event handlers associated with a component, enabling dynamic behavior in response to state changes or external events.
|
|
232
|
+
|
|
233
|
+
```tsx
|
|
234
|
+
builder.updateHandlers((handlers, state, setState) => ({
|
|
235
|
+
host: {
|
|
236
|
+
onClick: () => setState({ isActive: !state.isActive }),
|
|
237
|
+
},
|
|
238
|
+
}));
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
#### `addState(stateFn)`
|
|
242
|
+
|
|
243
|
+
Introduces state management capabilities to a component, allowing it to maintain and update its internal data.
|
|
244
|
+
|
|
245
|
+
```tsx
|
|
246
|
+
builder.addState((state, setState) => {
|
|
247
|
+
// Initialize state
|
|
248
|
+
if (!state.count) {
|
|
249
|
+
setState({ count: 0 });
|
|
250
|
+
}
|
|
251
|
+
|
|
252
|
+
// Expose a method to update the state
|
|
253
|
+
return {
|
|
254
|
+
increment: () => setState((prevState) => ({ count: prevState.count + 1 })),
|
|
255
|
+
};
|
|
256
|
+
});
|
|
257
|
+
```
|
|
258
|
+
|
|
259
|
+
#### `addEffects(effectsFn)`
|
|
260
|
+
|
|
261
|
+
Facilitates the integration of side effects into a component's lifecycle, such as data fetching, API interactions, or direct DOM manipulations.
|
|
262
|
+
|
|
263
|
+
```tsx
|
|
264
|
+
builder.addEffects((state) => [
|
|
265
|
+
{
|
|
266
|
+
effect: () => {
|
|
267
|
+
console.log('Component mounted!');
|
|
268
|
+
},
|
|
269
|
+
dependencies: [],
|
|
270
|
+
},
|
|
271
|
+
]);
|
|
272
|
+
```
|
|
273
|
+
|
|
274
|
+
#### `build(options)`
|
|
275
|
+
|
|
276
|
+
Finalizes the component building process, consolidating all applied customizations and returning a new, enhanced React component ready for use.
|
|
277
|
+
|
|
278
|
+
```tsx
|
|
279
|
+
const CustomizedComponent = builder.build();
|
|
280
|
+
```
|
|
281
|
+
|
|
282
|
+
### Combining Inversify and ComponentBuilder for Advanced Customization
|
|
283
|
+
|
|
284
|
+
This example demonstrates how to combine the power of Inversify and ComponentBuilder to achieve advanced component customization in a clean and maintainable way.
|
|
285
|
+
|
|
286
|
+
```tsx
|
|
287
|
+
import ComponentBuilder from './path/to/ComponentBuilder';
|
|
288
|
+
import Inversify from './path/to/Inversify';
|
|
289
|
+
|
|
290
|
+
import React, { FC } from 'react';
|
|
291
|
+
|
|
292
|
+
interface MyComponentProps {
|
|
293
|
+
title: string;
|
|
294
|
+
}
|
|
295
|
+
|
|
296
|
+
const MyComponent: FC<MyComponentProps> = Inversify.register('MyComponent', ({ title }) => (
|
|
297
|
+
<div>
|
|
298
|
+
<h1>{title}</h1>
|
|
299
|
+
<p data-customize-id="content">Default content</p>
|
|
300
|
+
</div>
|
|
301
|
+
));
|
|
302
|
+
|
|
303
|
+
Inversify.resolve(MyComponent.original).bind((originalComponent) =>
|
|
304
|
+
ComponentBuilder.use(originalComponent)
|
|
305
|
+
.updateStyles(() => ({
|
|
306
|
+
component: {
|
|
307
|
+
border: '1px solid blue',
|
|
308
|
+
padding: '10px',
|
|
309
|
+
},
|
|
310
|
+
}))
|
|
311
|
+
.updateHTML({
|
|
312
|
+
content: () => <span>Customized content!</span>,
|
|
313
|
+
})
|
|
314
|
+
.build(),
|
|
315
|
+
);
|
|
316
|
+
|
|
317
|
+
// IMPORTANT: From this point onwards, any usage of MyComponent will
|
|
318
|
+
// actually render the customized version created by ComponentBuilder.
|
|
319
|
+
```
|
|
320
|
+
|
|
321
|
+
**Explanation:**
|
|
322
|
+
|
|
323
|
+
1. **Registration:** We start by wrapping our `MyComponent` with `Inversify.register`, making it customizable.
|
|
324
|
+
2. **Resolution and Binding:** We use `Inversify.resolve` to access the registered component and then chain the `bind` method.
|
|
325
|
+
3. **ComponentBuilder Customization:** Inside the `bind` method's factory function, we use `ComponentBuilder` to:
|
|
326
|
+
- Add a blue border and padding to the component's root element using `updateStyles`.
|
|
327
|
+
- Replace the content of the `p` tag marked with `data-customize-id="content"` using `updateHTML`.
|
|
328
|
+
4. **Implicit Replacement:** The crucial point here is that we don't explicitly call `render()` after the `bind` operation. This means that Inversify will seamlessly replace all future instances of the original `MyComponent` with our customized version.
|
|
329
|
+
|
|
330
|
+
This combined approach not only allows you to leverage Inversify's implementation swapping capabilities while harnessing the structured customization features of ComponentBuilder but also highlights how Inversify can be used for implicit, application-wide component modifications.
|
|
331
|
+
|
|
332
|
+
This combined approach enables you to use Inversify's implementation swapping features along with the structured customization options provided by ComponentBuilder. Additionally, it emphasizes how Inversify can be employed for implicit, application-wide modifications of components.
|
|
333
|
+
|
|
334
|
+
### Conclusion
|
|
335
|
+
|
|
336
|
+
In conclusion, **Inversify** and **ComponentBuilder** offer powerful mechanisms to enhance the flexibility, maintainability, and customization potential of your React components. By providing tools to manage implementations, structure component logic, and simplify complex customizations, these libraries streamline the development process and promote code clarity, ultimately leading to more robust and adaptable React applications.
|
|
337
|
+
|
|
338
|
+
## Contributing
|
|
339
|
+
|
|
340
|
+
We invite contributions from the community to further enhance Modulify-UI! Whether you've discovered a bug, have a suggestion for improvement, or wish to contribute code, we encourage your involvement.
|
|
341
|
+
|
|
342
|
+
- **Bug Reports:** Should you come across any issues or unexpected behavior, we encourage you to open an issue on our GitHub repository. Please provide a clear description of the problem and detailed steps to reproduce it.
|
|
343
|
+
- **Feature Requests:** Have a great idea for a new feature or improvement? Feel free to open an issue to discuss it with the community.
|
|
344
|
+
- **Code Contributions:** We welcome pull requests for bug fixes, new features, or documentation improvements. Please ensure your code follows the existing style guidelines and includes appropriate tests.
|
|
345
|
+
|
|
346
|
+
We appreciate your contributions and look forward to building a robust and versatile UI toolkit together!
|
package/index.esm.d.ts
ADDED
|
@@ -0,0 +1 @@
|
|
|
1
|
+
export * from "./src/index";
|