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

Suggestion: Add a 'flag for deprecated code' global option allowing for easier upgrade #6846

Closed
Ruffio opened this Issue Dec 25, 2013 · 5 comments

Comments

Projects
None yet
4 participants
@Ruffio

Ruffio commented Dec 25, 2013

I just an idea. When upgrading from one version to another often methods, default values etc. are changed to align code/wording. As applications gets bigger and bigger it can often be difficult/time consuming to analyse which code is now deprecated. My suggestion is that if a global value 'flagForDepricatedCode' is set true, then every time deprecated code (only from previous version) is executed in browser, then a message is written to console which deprecated code was reached. That would allow developers to easy 'take a walk around the application' and get a (complete) list of deprecated/soon to be deprecated code that needs attention.

I know it's a wild shot, so no hard feelings if the idea isn't implemented :-)

@jamesjnadeau

This comment has been minimized.

Show comment
Hide comment
@jamesjnadeau

jamesjnadeau Dec 26, 2013

I like this idea, especially with all the proposed changes that are coming down the pipe.

jamesjnadeau commented Dec 26, 2013

I like this idea, especially with all the proposed changes that are coming down the pipe.

@teusink

This comment has been minimized.

Show comment
Hide comment
@teusink

teusink Jan 4, 2014

Same here. Would be really helpfull!

teusink commented Jan 4, 2014

Same here. Would be really helpfull!

@Ruffio

This comment has been minimized.

Show comment
Hide comment
@Ruffio

Ruffio Apr 17, 2014

I guess that, when jquery-mobile-event-debugger is implemented then this issue can be closed.

Ruffio commented Apr 17, 2014

I guess that, when jquery-mobile-event-debugger is implemented then this issue can be closed.

@Ruffio

This comment has been minimized.

Show comment
Hide comment
@Ruffio

Ruffio Oct 13, 2014

As we have multiple functions depricated in 1.4.4 that are removed in 1.5.0, why not implement this in 1.4.5, so dev. get used to using it for 1.5.0 where a lot more is depricated?

Ruffio commented Oct 13, 2014

As we have multiple functions depricated in 1.4.4 that are removed in 1.5.0, why not implement this in 1.4.5, so dev. get used to using it for 1.5.0 where a lot more is depricated?

@arschmitz

This comment has been minimized.

Show comment
Hide comment
@arschmitz

arschmitz Jun 19, 2015

Member

So we actually have done this already in 1.5 but just found this issue. all backcompat code is now in its own modules and can also be disabled by setting $.mobileBackcompat = false before jQuery mobile is loaded. Im going to close this as fixed.

Member

arschmitz commented Jun 19, 2015

So we actually have done this already in 1.5 but just found this issue. all backcompat code is now in its own modules and can also be disabled by setting $.mobileBackcompat = false before jQuery mobile is loaded. Im going to close this as fixed.

@arschmitz arschmitz closed this Jun 19, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment