-
-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
afFieldValueIs Helper: Cannot read property 'schema' of undefined #753
Comments
Hi please link to a reproduction repo or MeteorPad. The tutorial you link to is currently using af5 and does not have that error. |
I have seen this error when using afFieldIsInvalid ... not sure if legitimate bug or developer error though. |
Also having this error after updating to af5. All caused by afFieldLabelText, afFieldIsInvalid and afFieldMessage. So I reverted back to af4.2.2 and there's no more error. |
Can someone post full reproduction code? |
I can not reproduce it due to complicated code. But what I found (I have same error after upgrade to af5), that AutoForm.getFormSchema() return 'undefined' in parseOptions function. Hope it helps... and my AutoForm in html has the following attrs: |
I have tried to reproduce it in MeteorPad, but it works normally. The difference is MeteorPad has 1.0.2.1 version of Meteor. And I have above problem on 1.0.4.1 |
I have this poblem on Meteor 1.0.4.1 & af5.0.2 I happens with afFieldValueIs and when you have here is the link to the repo with this error reproduced: https://github.com/shkomg/autoform-demo |
@aldeed I've posted full reproduction code in the post above. Thank you. |
Seems like duplicate of #790. AF isn't compatible 1.0.4.1 pending some kind of fix or solution from MDG. |
New AF release is compatible with 1.0.4+ and should get rid of this error. |
I'm quite new to Meteor and I just stumbled upon this error when using the afFieldValueIs Helper:
Exception in template helper: TypeError: Cannot read property 'schema' of undefined
(I copied the tutorial from http://autoform.meteor.com/fieldvalues and it worked like a charm before the update of autoform)
kind regards
ps: sorry for my bad English :)
The text was updated successfully, but these errors were encountered: