e.g. isPassportNumber, etc.

The currently published docs on redux-form.com has its Examples page returning a "404" page:

https://redux-form.com/8.3.0/examples/

And, if you click on the example links in the nav sidebar, such as the Simple Example at https://redux-form.com/8.3.0/examples/simple/ then all of the sidebar links become /8.2.2/ instead of /8.3.0/

Versions

• vee-validate: 3.1.3
• vue: 2.6.10
• vue-jest: 3.0.5
• @vue/test-utils: ^1.0.0-beta.31

Describe the bug
I have a BaseInput.vue component which has one default <slot></slot> wrapped in a <validation-provider>. When it has errors it will show the error message inside a <div class="error-message"></div>.
But, in my tests, when I pass a <input> to the default slo

Hey Erik! How's it been?

Are you submitting a bug report or a feature request?

Feature

What is the current behavior?

No mention of withTypes in the documentation.

What is the expected behavior?

༼ つ ◕_◕ ༽つ

I just found out about this from a co-worker and am not even sure yet what it exactly was! Excited to see..

This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:

$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin

Add more doc in the code urgent the Validator class

This tools is great, we can define and validate various config from file, env, cli arg... and we can even put a short doc on each field.

But what if I want to display a clear and concise doc reference on a website on a cli usage?

Should this package be able to handle that? If not, is it compatible with other packages doing that need?

Thanks

I saw in test next example:

            var validator = new Validator({
                users: [{
                    name: 'Teste',
                    lastName: '',
                    age: '',
                    requiredAge: 'true',
                }]
            }, {
                'users.*.age': 'required_if:users.*.requiredAge,true',
                'users.*.lastNa

See: https://gist.github.com/ericelliott/f3c2a53a1d4100539f71

Advantages

See: https://medium.com/javascript-scene/you-might-not-need-typescript-or-static-types-aa7cb670a77b

• autocomplete and type inference with most IDEs
• doesn't require passing Log objects for every call (although it's encouraged)
• other non-required parameters (such as query) can be omitted
• much easier to a

alibaba-fusion Select component (https://github.com/alibaba-fusion/next) used as below:

const dataSource = [
  { label: 'option1', value: 'option1' },
  { label: 'option2', value: 'option2' },
  { label: 'disabled', disabled: true }
]

<Select dataSource={dataSource} />

<Select>
     <Option value="small">Small</Option>
     <Option value="medium">Medium</Option>
     <Option val

Currently, this monorepo consists of:

• babel-plugin-flow-prepack
• babel-plugin-flow-runtime
• flow-config-parser
• flow-runtime-cli
• flow-runtime-docs
• flow-runtime-mobx
• flow-runtime-validators
• flow-runtime

A subset of these provide the core functionality of flow-runtime:

• flow-runtime-validators
• flow-runtime
• flow-runtime-cli
• babel-plugin-flow-runtime

Meanwhile

@voltrue2 I think we should add some documentation for the validate method. I'm also happy to submit a PR for this. I'm receiving the following errors sometimes and it is unclear without investigating the code whether this means the request failed or if the receipt is invalid. In my particular case, both of these failures were for valid receipts.

{ Error: read ECONNRESET
    at TLSWrap.

Please add descriptions to functions in the source code, to make it easy to read and understand.

Example:

/**
 *   Transforms an input element....
 * @param {Function} successFn callback function in case of valid input
 * @param {Function} failFn callback function in case of invalid input
 * @param {Array} input
 * @returns {*}
 */
const transform = (successFn: Function, failFn

I'm trying to use Hyperform to detect when the form switches between an invalid and valid state so I can switch disabling of the submit button.

If I monitor the "valid" event on the form it keeps getting triggered even though elements within the form are still invalid.

If I run form.checkValidity() on startup each field will indicate an "invalid" event and checkValidity returns false. It see

Currently the example value can have a different data structure that is defined in the schema and the swagger-cli validate doesn't rise an error.

example:
    foo:
        bar: a
        baz: b
type: object
properties:
    foo:
        type: integer
        format: int32
        default: 0

I think it would be very useful if the example value would be validated against

doc.isModified('status.active') works when status exists as an object, and fails when status is undefined.
Is it intended? Seems to be a bug to me.

I'm trying to find out how to fit vue-mc into my app's architecture, and the docs are helpful, but maybe I am missing something obvious:

In the Vue docs data section, it reads:

A rule of thumb is that data should just be data - it is not recommended to observe objects with their own stateful behavior.

Where should I store my model instance otherwise?

https://github.com/af/envalid/blob/ad2f612ddef8b4a07d6b6d553f33aad21cbfb849/src/envalidWithoutDotenv.js#L34

In my company we use envalid but with non-default environment values. Thus, I got my builds failing with the error above.

Currently the function validateVar in envalidWithoutDotenv.js doesn't give a comprehensive error message with potential reasons for this issue and how to fix