Open pouya-eghbali opened 5 years ago
I will look t it end of this week. But it sounds like it can find a home here.
On 13 May 2019, at 18:47, Pouya Eghbali notifications@github.com wrote:
Currently we're making a .row for all fields and applying .s12 to all of them. I have a meteor package to fix this and add some extra functionality, for example grouping fields, adding a title for groups, defining field and field group orders and field size (width).
Here's how you can define any of these options, in your schema:
const schema = new SimpleSchema ({ fieldName: { type: fieldType, autoform: { group: "group-identifier", groupTitle: "title of the group", groupHelp: "help text", order: 0, groupOrder: 0, size: "m6 s12" } } }) This works very well in my projects, but the implementation isn't perfect. However, after reading the source code of your package I realised how easy it is to implement this feature in the package, so I locally implemented it and the result is really nice. I'd like to know if we can put this functionality in your package or should I maintain my own fork of the package?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/mozfet/meteor-autoform-materialize/issues/73?email_source=notifications&email_token=ABHALGEN5JUDMWZ36WRQRJTPVGLQJA5CNFSM4HMRTPMKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GTPIUOQ, or mute the thread https://github.com/notifications/unsubscribe-auth/ABHALGE7YHKWG3U63I5FRJTPVGLQJANCNFSM4HMRTPMA.
Currently we're making a
.row
for all fields and applying.s12
to all of them. I have a meteor package to fix this and add some extra functionality, for example grouping fields, adding a title for groups, defining field and field group orders and field size (width).Here's how you can define any of these options, in your schema:
This works very well in my projects, but the implementation isn't perfect. However, after reading the source code of your package I realised how easy it is to implement this feature in the package, so I locally implemented it and the result is really nice. I'd like to know if we can put this functionality in your package or should I maintain my own fork of the package?