wearebraid / vue-formulate-legacy Goto Github PK

Please refer to the initialization of the example form in my Pull Request to understand the problem.

Removing any one of lines 9 -> 14 in the file example/src/App.vue will cause some sort of deadlock that will consume all of available browser memory.

Currently direct mutations of the store to inject field values is possible by using the {module}/setFormField mutation. However, validation routines are currently triggered outside of the store in the Formulate element meaning that direct store mutations do not properly trigger validation events. This is really a bug since performing direct mutations is absolutely within the scope of this project.

We should first address this issue before adding the documentation request in issue #3.

I was wanting to use vue-cleave.

How would I combine

<cleave placeholder="Enter your credit card number" :options="{ creditCard: true }"></cleave>

and

<formulate-element type="number" name="creditCard" label="Credit Card Number"/>

into a single input?

According to GitHub the latest release is 0.7.4
According to NPM the latest release is 0.8.0

I am using Buefy & Bulma

To style an element as a button with standardized colors, one can do:

<input class="button is-primary" type="submit" value="Submit input">

Unfortunately, if I try to do ...

<formulate-element class="button is-primary" type="submit" name="Save"/>

... I get an unstyled button sitting within a div styled with 'is-primary'.

<div class="button is-primary formulate-element formulate-element--type--submit">
    <div data-type="submit" data-classification="button" class="formulate-element-input-wrapper">
        <!---->
        <!---->
        <button type="submit">Save</button>
        <!---->
        <!---->
        <!---->
        <!---->
    </div>
    <!---->
</div>

Could you for example, provide formulate-element with an attribute, inner-element-class, whose value is added to the class attribute of formulate-element's underlying button/input/select/etc ?

The docs and demo need to show the steps to mutate the store so that the form is filled.

Is there a mutation for the entire form? Must it be mutated one field at a time?

Where is the namespace used and how?