
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
@gpx/render-composer
Advanced tools
When working with Testing Library within a large project often you need to wrap your component in several providers:
const history = createMemoryHistory();
const locale = 'en';
const user = {name: 'Giorgio'};
render(
<Router history={history}>
<IntlProvider locale={locale}>
<UserContext.Provider value={user}>
<MyComponent />
</UserContext.Provider>
</IntlProvider>
</Router>,
);
This can lead to a lot of overhead and is not very flexible.
Render Composer allows you to declare reusable and configurable wraps that define a single provider. These wraps can then be combined to generate more complex hierarchies.
const RouterWrap = wrap((children, {history}) => (
<Router history={history}>{children}</Router>
)).defaultData(() => ({
history: createMemoryHistory(),
}));
const IntlWrap = wrap((children, {locale}) => (
<IntlProvider locale={locale}>{children}</IntlProvider>
)).defaultData({locale: 'en'});
const UserWrap = wrap((children, {user}) => (
<UserContext.Provider value={user}>{children}</UserContext.Provider>
)).defaultData({user: {name: 'Giorgio'}});
const appRender = RouterWrap.wraps(IntlWrap)
.wraps(UserWrap)
.withRenderMethod(render);
appRender(<MyComponent />);
With NPM:
npm install @gpx/render-composer --save-dev
With Yarn:
yarn add @gpx/render-composer --dev
Now simply import it in your tests:
import wrap from '@gpx/render-composer';
// or
var wrap = require('@gpx/render-composer');
You can create a wrap with the wrap
method:
const Wrap = wrap((children, data) => <div>{children}</div>);
data
is an empty object by default. You can set some default values with defaultData
:
Wrap.defaultData({foo: 'bar'});
If you need the data to be generated every time rather than be static you can also
pass a function to defaultData
:
Wrap.defaultData(() => ({foo: Math.random()}));
You can compose the wraps with the wraps
method. You can chain as many wraps you want:
WrapA.wraps(WrapB)
.wraps(WrapC)
.wraps(WrapD);
Once you are satisfied with your wrap you can get a render method with withRenderMethod
:
import {render} from '@testing-library/react';
const renderWrap = Wrap.withRenderMethod(render);
renderWrap(<MyComponent />);
The generated render method will also accept data to overwrite the default values you defined in your wraps. The data will be returned too:
Wrap.defaultData(() => ({foo: 'bar'}));
// This `foo` will have value `'bar'`
const {foo} = renderWrap(<MyComponent />);
// This `foo` will have value `'baz'`
const {foo} = renderWrap(<MyComponent />, {foo: 'baz'});
Note that wraps are immutable so that they can be defined in one file and exported and combined.
FAQs
Create complex renders for react-testing-library
The npm package @gpx/render-composer receives a total of 1 weekly downloads. As such, @gpx/render-composer popularity was classified as not popular.
We found that @gpx/render-composer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.