stewie1570 / leaf-validator Goto Github PK

A test to verify callback form of setState works properly.

Objective is to lower the package size and increase performance at the same time.

If the package consumer supports ESM then the consumer should support a higher compilation target than the default of ES3.

Diff currently builds complex objects by setting root properties to a whole complex object. Each diff should be scoped all the way to a single leaf.

From minified to minzipped.

const [isLoading, doLoad] = useLoadingState(loadingFunction);

doLoad type definition from loadingFunction type def.

After the next release of react-scripts you should be able to remove --env=jest-environment-jsdom-sixteen from scripts and remove jest-environment-jsdom-sixteen from devDependencies.

New Feature Idea 💡

For backward compatibility with persistence layer:

Leaf should use the first defined failOverLocations in the model when the location in the model is undefined.

{
...
"main": "cjs/index.js",
"module": "esm/index.js",
...
}

Validators can be async. As such, they could resolve after the component is un-mounted and cause un-mounted state change warnings/errors.

useMountedOnlyState instead of useState.

Undefined location should query same as an empty string location.

The link to example diff usage that navigates to the mongo/leaf-validator example should link directly to the line that calls the diff function:

Like this:
Example

The hook already has an optional/configurable deferment of starting the loading state but there should also be an optional/configurable amount of minimum loading time.

For use with react...

Non open source projects should be able to use this.

Example from the example app:

[
    {
        "location": "deferredAsyncValidation",
        "messages": [
            "Value is required"
        ]
    },
    {
        "location": "asyncValidation",
        "messages": [
            "\"undefined\" is not valid."
        ]
    },
    {
        "location": "deferredAsyncValidation",
        "messages": [
            "\"undefined\" is not valid."
        ]
    }
]

deferredAsyncValidation has two objects because there are two namespaces for those validators (deferred and not deferred).

• Encourages normalization - link to Redux docs.

• Encourages best practices documented by Redux (but without as much overhead since reducers are implemented declaratively).

• Merge

• Release (v3.6.2)

React error boundaries do not catch rejected promises. Create a component that will catch errors and unhandled rejections in its children composition.

This is testing a new instance of the component....Not necessary.

This is testing a whole new instance of the component that use mounted-only-state.

• Include documentation about validation model queries.
• Find some full stack examples to include.
• Split-up the docs and organize readme files into the code file system.

Same as use state but state setters turn into No Ops when the component is not mounted.

useLoadingState should use this.

omg, how embarrassing. The methods in the validation model take model shape and validation results as a parameters. It has no need for the model itself. How did I miss this?

Validation could be called multiple times before the first validation resolves. Only the latest validation results should be applied to the validation model.

Similar to https://www.npmjs.com/package/react-error-boundary but can support displaying multiple errors at the same time and does not change the child component composition.

• Implementation

• Documentation

• Publish

This can just await the configured amount of time before setting loading to true since the operation promise is already inflight when the hook function is invoked.

• Refactor to promise async composition instead of callbacks.

• Merge

• Release (v3.6.2)

Currently appears to process the whole object even if the root is referencing the original.

[Get & Set pure functions](#get-&-set-pure-functions) works in VSCode but not GitHub or NPMJs.com

• Split-up the docs and organize readme files into the code file system.
• Include documentation about validation model queries.

It would be nice to have source control & ci in one cohesive place. Plus the travis-ci badge is randomly showing failed even though its passing and it is starting to piss me off.

• Pass location as a parameter to child render function of Leaf component.
• Look for improvement.
• Merge and publish.

To invoke the effects just like deferred validators.

This attribute should only run the validators after some fixed amount of time after the last target value change. The validators should not be run again until they've all resolved.

Create (& export) a function that can take the current model, the original model and return a list of key-value-pairs. The keys being progressed value locations and the value being the current value for that location.

Appears related to: facebook/create-react-app#9583

Causing build failure on my mac.

• Investigate

• Fix

• Merge

No need to publish - package build time problem only.