Issue 352 in iui: ** feature request** expose encodeForm api

0 views
Skip to first unread message

i...@googlecode.com

unread,
Jan 1, 2013, 9:42:24 PM1/1/13
to iui-i...@googlegroups.com
Status: New
Owner: ----

New issue 352 by ldar...@gmail.com: ** feature request** expose encodeForm
api
http://code.google.com/p/iui/issues/detail?id=352

is it possible to expose encodeForm to the public? it is useful when iui is
the only js framework being used

i...@googlecode.com

unread,
Jan 3, 2013, 3:08:30 AM1/3/13
to iui-i...@googlegroups.com
Updates:
Status: Accepted

Comment #1 on issue 352 by msgilli...@gmail.com: ** feature request**
This is a reasonable request. The main reason I haven't exposed the method
is that it hasn't been tested as a general-purpose method and I haven't
wanted to guarantee it will not be changed in the future. It has improved
over time and given that some people use iUI ad their only JS framework, it
might make sense to export it.

(Looking over on GitHub I see that a pull request might be in my future...)


i...@googlecode.com

unread,
Jan 3, 2013, 7:48:17 PM1/3/13
to iui-i...@googlegroups.com

Comment #2 on issue 352 by ldar...@gmail.com: ** feature request** expose
encodeForm api
http://code.google.com/p/iui/issues/detail?id=352

nice, which one is your current "develop" branch? should i send the pull
request to your master or feature-node branch?

i...@googlecode.com

unread,
Jan 4, 2013, 2:29:43 AM1/4/13
to iui-i...@googlegroups.com

Comment #3 on issue 352 by msgilli...@gmail.com: ** feature request**
master is the current development branch, send the pull request there.




Reply all
Reply to author
Forward
0 new messages