-
Notifications
You must be signed in to change notification settings - Fork 76
Support InputFor inside InputGroup #59
Comments
So back to the question of how to use an |
I guess However, I still think For now, it's easier to just write the whole block of |
That makes sense, and should be doable. Unlike |
Fantastic, I'll fork and see if I can make any headway into it as well. |
Hi, im interested on this issue, so I' ve forked the repo and i'm going to make a pull request....i'm not sure if this the right way to do it because it's my first pullrequest on an external library. ^_^U Hope u can check and merge if u think that is right. Thank u so much. |
Resolved by #64 |
I'll try and remember to do a release next week - feel free to ping me if I forget. |
Great. Thx for your work. |
Hi @daveaglick , dont forget to do a release plz! :) |
@daveaglick any news about the release? Thx. |
Sorry for the delay, got busy - 3.3.5.4 is now out |
Np, thx for releasing the new version. :) _David Bueno Rincón_www.evicertia.com| david@evicertia.es 2016-09-27 20:04 GMT+02:00 Dave Glick notifications@github.com:
|
Is it possible for InputGroups to support EditorFor and InputForm elements.
Or if the EditorFor can also have a InputGroupAddon()
The text was updated successfully, but these errors were encountered: