nicolaslopezj / meteor-react-form Goto Github PK

• String
• Number
• Date
• Boolean
• Object
• [String]
• [Number]
• [Date]
• [Boolean]
• [Object]

Hi Nicolas,
cool work!

The package should export the components also on the server to enable SSR (e.g. with FlowRouter SSR).

Maybe this might be solved when we switch to npm?

Support with array type of schema (add more form)?

contacts: {
    type: Array,
    optional: true
  },
  'contacts.$': {
    type: Object
  },
  'contacts.$.name': {
    type: String
  },
  'contacts.$.phone': {
    type: String
  }

I think this project is a great job for meteor react developers.
But I found it's hard to follow the README document to use this package.
Could you please provide a little sample app which includes basic insert and update.

Thanks!

Have any pre install or not such as materail ui package?
I get error

=> Meteor server restarted                                              
W20160227-15:04:25.718(7)? (STDERR) Error when doing SSR. path:/post-cre
ate: Cannot read property 'Form' of undefined                           
W20160227-15:04:26.055(7)? (STDERR) TypeError: Cannot read property 'For
m' of undefined                                                         
W20160227-15:04:26.055(7)? (STDERR)     at new PostCreate (app/component
s/post_create.jsx:7:6)                                                  

For some reason I get an error. As soon as I add mrf attribute to SimpleSchema field, like:

    mrf: {
      type: 'textarea',
    }

Error: Invalid definition for body field.
at packages/aldeed_simple-schema/simple-schema.js:457:1

I installed:
nicolaslopezj:mrf
nicolaslopezj:mrf-material-ui

Any idea why I get this error?

When displaying a date value in update mode, I get:
The specified value "Wed Feb 24 2016 21:56:31 GMT+0100 (CET)" does not conform to the required format, "yyyy-MM-dd".

The default date format should be enforced in MRF, right?

Support custom input field like:

<div class="col-md-6">
                {{> afQuickField name='khName'}}
                {{> afQuickField name='khShortName'}}
                {{> afQuickField name='enName'}}
                {{> afQuickField name='enShortName'}}
                {{> afQuickField name='khAddress' row=3}}
            </div>

Even if it's maybe early for that, it would be nice to support 1.3 (and Mantra?).
For example, the new testing capabilities could be used.

I did some experiments with beta.6/Mantra and had these issues so far:

• incompatibility with wallaby.js file (just removed the file for now but a more detailed analysis is required)
• could not solve the multiple react copies loaded puzzle (see for example mui/material-ui#2818)... can we still use legacy packages pulling React or do we have to use npm instead?

It looks like these will have to be fixed before going further with 1.3... a specific branch will probably be required.

Thank you for this key package!

Correct doc on Posts.attachSchema(new SimpleSchema(......)).

Using the schema basic example from the README file, I currently get on the server-side:
Error: Invalid definition for createdAt field.

IMO, this new optional mrfoption is added on client side only (init.jsx) but it is required on server side too.
This should rather be defined in a .js file loaded on both client and server sides.