-
-
Notifications
You must be signed in to change notification settings - Fork 140
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
Checklist #1
Comments
The only thing I can think of offhand is that the keys need to be the same data type - that is, they need to both be strings. But I'd assume you know that already, and that your stored JSON data from which you're restoring values is actually encoded as |
this might be a little boring for you .. but here goes ... (also I've gone back and forth on the quotation marks -- it makes no difference - and it works on the other form types. this is part of a data structure with test data
in the view I have the following snippet;
In my controller I have;
You have seen my service, but I'll reprint (Every is working correctly except for the checklist)
|
fyi -- I just tried it exactly like you suggested "region": {"1": true} and no joy. |
I was thinking of strict JSON, which requires object property names to be capitalized... The notation used within JavaScript is considerably more forgiving. I think I found the issue, though... Stupidly, I'm setting the model value to |
… compile Resolves GitHub issue #1 Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
… compile Resolves GitHub issue #1 Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
That should fix it. Care to give it a try? |
Sxsw baby (I’m in austin.tx)— I’ll try in the morning if you don’t mind — thanks for your help — really nice work … (I’ll let you know) |
not that I’m pushing (I’m not — I’m very happy with what you have achieved) … as an alternative I tried the select with the muiltiple option — it either has the same problem or I couldn’t figure out how to configure the object. |
The way Angular handles model values for various form elements isn't necessarily intuitive. For a While the way Angular sets up models for form elements is outside my control, and therefore the scope of this module's documentation, I really should document how my code sets up models for the handful of "elements" I made up ( |
nicely working. thanks for your help. |
just so you are aware, I think there may be a bug on the line you revised. If I pass in a {} model - I get a type error:
|
I might be wrong — In a subsequent test, I’m not observing this — must be something with one of my objects. |
Since it sounds like this error didn't reappear, I'll close this issue. Feel free to reopen it if needed. |
Addresses BitBucket issue #1 Seeing if creating the elements (`ng-form` specifically, but also the various templated elements in case we decide to add nonstandard ones later, though I'd prefer not to, at the moment...) *before* handing them to jqLite/jQuery (rather than having the jQ* lib handle element creation from raw HTML) will make IE versions before 9 (specifically 8, but I'll also test older versions if I can, once it works in 8) actually treat the elements as usable - at the moment they cannot have children, for some reason. Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
Addresses BitBucket issue #1 Further testing in IE 8 showed that more elements needed to be created manually instead of by jQuery/jqLite. Also updated the README with steps for IE 8 support. IE 6 and 7 have limited support, even for Angular itself. Neither version will be targeted in the near future. IE 8 support is still not a guarantee, especially since Angular will only partially support it themselves, but it is much stronger than it was. Updated the demo project with the IE 8 "hacks" needed to get it working in that browser. Signed-off-by: Daniel Hunsaker <danhunsaker@gmail.com>
Hi -- I'm trying to populate my check list from stored json data
region: {1:true}
But it isn't being checked in the form;
Any thoughts ?
I have other components and they are populating correctly.
tony@drillmap.com
The text was updated successfully, but these errors were encountered: