Security News
GitHub Removes Malicious Pull Requests Targeting Open Source Repositories
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
forgo-state
Advanced tools
Easy Application State Management for [Forgo Apps](https://github.com/forgojs/forgo) using JavaScript Proxies.
Easy Application State Management for Forgo Apps using JavaScript Proxies.
npm i forgo-state
Start by defining one or more state variables using the defineState() API. These states can be bound to multiple components in the application.
import { bindToStates, defineState } from "forgo-state";
const mailboxState = defineState({
messages: [],
drafts: [],
spam: [],
unread: 0,
});
const signinState = defineState({
username: "",
lastActive: 0,
});
Use bindToStates() to bind one or more states to any component. In the following example, whenever mailboxState or signinState changes, the bound component MailboxView is rerendered. Similarly, NotificationsBar is also bound to mailboxState.
function MailboxView() {
const component = {
render(props: any, args: ForgoRenderArgs) {
return (
<div>
{mailboxState.messages.length ? (
mailboxState.messages.map((m) => <p>{m}</p>)
) : (
<p>There are no messages for {signinState.username}.</p>
)}
</div>
);
},
};
return bindToStates([mailboxState, signinState], component);
}
function NotificationsBar() {
const component = {
render() {
return (
<div>
{mailboxState.unread > 0 ? (
<p>You have {mailboxState.unread} notifications.</p>
) : (
<p>There are no notifications.</p>
)}
</div>
);
},
};
return bindToStates([mailboxState], component);
}
You could update the state properties directly:
async function updateInbox() {
const data = await fetchInboxData();
// The next line causes a rerender of the MailboxView component
mailboxState.messages = data;
}
Sometimes, you're interested in rerendering only when a specific property of a state variable changes. There's another api for this, bindToStateProps().
Usage is similar. But instead of an array of states you're interested in, you'll have to pass an array of [state, propertiesGetter] tuples.
Here's an example:
function MailboxView() {
const component = {
render(props: any, args: ForgoRenderArgs) {
return (
<div>
{mailboxState.messages.length ? (
mailboxState.messages.map((m) => <p>{m}</p>)
) : (
<p>There are no messages for {signinState.username}.</p>
)}
</div>
);
},
};
return bindToStateProps(
// Render only if mailboxState.messages or mailboxState.drafts
// or signinState.username changes.
[
[mailboxState, (state) => [state.messages, state.drafts]],
[signinState, (state) => [state.username]],
],
component
);
}
FAQs
Easy Application State Management for [Forgo Apps](https://github.com/forgojs/forgo) using JavaScript Proxies.
The npm package forgo-state receives a total of 0 weekly downloads. As such, forgo-state popularity was classified as not popular.
We found that forgo-state demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers 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
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.
Security News
RubyGems.org has added a new "maintainer" role that allows for publishing new versions of gems. This new permission type is aimed at improving security for gem owners and the service overall.
Security News
Node.js will be enforcing stricter semver-major PR policies a month before major releases to enhance stability and ensure reliable release candidates.