search

vue-generators / vue-form-generator

:clipboard: A schema-based form generator component for Vue.js
MIT License
2.99k stars 532 forks source link

V3 plans #348

Open icebob opened 6 years ago

icebob commented 6 years ago

Plans:

Any new idea?

Ping @lionel-bijaoui @cristijora @dflock @zoul0813

Branch: https://github.com/icebob/vue-form-generator/tree/v3

goatandsheep commented 5 years ago

@zoul0813 yup! Thanks. I just didn't see the feature in the docs and was unsure if it was ready

zoul0813 commented 5 years ago

@goatandsheep didn't realize this functionality was still missing from the documentation.

Will gladly accept a PR to the vue-form-generator-docs repo for it.

goatandsheep commented 5 years ago

@zoul0813 sure! I'll do a docs PR

vesper8 commented 5 years ago

really looking forward to attributes, and other new additions to v2, being merged into v3 as well :) I've been using v3 in production for a few months now.. against recommended advice I understand.. and it's great

zoul0813 commented 5 years ago

@vesper8, I was pretty sure attributes were merged into v3 per the discussion above... is that not true?

Any chance you can do a reasonable PR that merges that single functionality?

goatandsheep commented 5 years ago

@icebob re:vue-table-generator, what if we made a table generator that uses the same schema, but then only displays the attributes where featured: true? We need a standardized schema that can be used in a versatile way.

icebob commented 5 years ago

@goatandsheep the plan was that table generator uses different schema because you want to format fields in different ways (e.g. show badges instead of normal text, or merge 2-3 fields into one...eg. I wanted to expose this component to an individual one. It generates table from this schema.

goatandsheep commented 5 years ago

@icebob I get the different formatting, but that means that for a given asset, we'd have to make a schema for displaying attributes on a table and a second schema for editing in the form. My understanding was that the schema was just supposed to help the library understand the incoming data better. Is there any way we could make the table schema attributes consistent with the form schema attributes? For example, title --> label, field --> model, etc.

icebob commented 5 years ago

If you merge the two schemas to one, how you can control the order of table columns and form fields (if you want different orders) You should use a new order property, as well, right?

goatandsheep commented 5 years ago

@icebob true, completely merging would remove a lot of the features, but it would be advantageous for those like myself who don't want that level of customizability to allow the schema to be used twice by having consistent attribute naming where possible.

zoul0813 commented 5 years ago

Let’s move the table discussion to its own issue, we can mark as a feature request?

mperumalswamy commented 5 years ago

Is there any plans when would this version be released?

zoul0813 commented 5 years ago

Not at the moment no, unfortunately, I think the dev whose been doing the bulk of the work is on hiatus at the moment, and I don’t have the time to pick things up where he left off.