Please activate JavaScript in your browser.
?
Success
Success
continuous-integration/drone
the build was successful
Details
Success
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
User tests:
Successful:
Unsuccessful:
Summary of Changes
Extend JInput
from Joomla\Input\Input
Deprecate JInput
classes for the namespaced variants
Testing Instructions
Reading data from the request works still
Documentation Changes Required
Note deprecations
mbabker
-
open
-
23 Oct 2016
mbabker
-
change
-
23 Oct 2016
joomla-cms-bot
-
change
-
23 Oct 2016
joomla-cms-bot
-
change
-
23 Oct 2016
Category
⇒
Libraries
Unit Tests
mbabker
-
change
-
26 Oct 2016
Title
Differences
…
Deprecate JInput in favor of the Framework's Input package
[4.0] Deprecate JInput in favor of the Framework's Input package
mbabker
-
edited
-
26 Oct 2016
joomla-cms-bot
-
change
-
26 Oct 2016
wilsonge
-
change
-
29 Oct 2016
Status
Pending
⇒
Fixed in Code Base
Closed_Date
0000-00-00 00:00:00
⇒
2016-10-29 20:52:59
Closed_By
⇒
wilsonge
wilsonge
-
close
-
29 Oct 2016
wilsonge
-
merge
-
29 Oct 2016
zero-24
-
close
-
29 Oct 2016
Add a Comment
Login with GitHub to post a comment
Is it worth extending JInputCli from framework Cli (and the others too) instead of JInput? I can see pros and cons both ways..... unsure how many people will practically typehint JInput....