What Are The Consequences of Using "Deprecated Code" In Flutter? - flutter

I recently upgraded to Flutter 2.0. I have dozens of Flatbuttons that are now deprecated. It's going to take me a few days to fix them all. What are the consequences of shipping an update before then with deprecation warnings? The app still builds and runs fine.

Basically this code will be deleted in future releases of flutter/flutter packages. Most of the time, api's get deprecated when a bug that requires a completely new implementation that will break compatibility or a better implementation that will break compatibility.
Therefore, you can use deprecated code but you should be very careful as they are not maintained and might stop working or deleted in the future. So as long as you are not updating versions you should be fine but it is highly unadvisable.

The problem is that your code will be updated and the flutter will no longer support this widget.
But flutter 2.0 has a tool to help with that. Run the command on your terminal to see what has been depreciated and needs to be updated.
dart fix --dry-run
And execute this other command for fix the depreciated items.
dart fix --apply
For more details about fix, click here

Related

What are the effects of "deprecated API" error on flutter?

My code show this error. I didn't use "flutter_secure_storage" dependency but it shows this error. But the app is working well, What is the reason for this and how to fix this also if didn't fix this, the effect of this error?
flutter_secure_storage is a plugin which uses platform specific APIs to interact with the device.
This warning suggests that it is using a deprecated Java API on the Android device. You can't really fix it unless you know Java and are willing to contribute to the plugin. At the same time, you can safely-ish ignore it for now: even deprecated APIs usually last a long time, and it won't affect any functioning until the underlying API is actually removed.
The best thing to do is regularly check for updates to the package, which might fix this warning.
As the error suggests, the package flutter_secure_storage use the file specified in the error, which in turn use or implements a deprecated API.
You might not use that plugin, but you are using some other plugin that use it.
You are not affected by it now because it is just a warning/information.
You could get affected by it when the depreciation goes to be removed instead. But by that time the package will have been updated. So all you have to do is update the package at a later time when said deprecation has been solved.

Is there a list of Stable Widgets?

Is there a list of Flutter stable widgets?
I've found several lists of nice flutter widgets, but as many of them have just been released, I'd like to select the stable ones and build over them. This way I'll keep the newer versions for a future version of my App.
You probably want to select a specific Flutter build release channel:
master & dev are probably not what you are looking for as they get updates basically as soon as possible (dev only once fully-tested)
beta has most of the latest functionality but the most stable / "best [..] build of the previous month"
stable. If you were really concerned, you could choose this, however, this will lack features of the pat few months.
In general, everything that makes it to beta has proven to be pretty "stable". Flutter uses continous integration and is pretty well-tested.
All of the official Flutter widgets should work without any issues and if you ever encountered an "unpredictable" bug, you could just open an issue or fix it yourself.

Do Unity functions that are obsolete still work.

So I am converting a project from Unity 4.x to 5.x and there are a number of functions that the Unity compiler is warning me that are no longer supported or are obsolete.
My question is do these functions still work? (even though they are marked as obsolete)
I know at some point they need to be updated to the newer API but for the moment I just need to fix the bugs so that the game works. Are these functions still usable? or are they potentially the source of runtime bugs?
Thanks
All obsolete functions has been replaced with new functions. So should take a backup and update your project. Go to Assets->Run API Updater, if your project in not getting updated automatically. Dont worry unity will take care of most of the things.
Yes, it's still work ! They just only warning it.
But i suggest you should change for better result, Unity 5 will update you code from old project, then you should change it following warning, just replace
using "xxxx" instead.
to the current context.

Activity stream missing after JIRA upgrade

I upgraded our JIRA from version 6 to version 6.1. Suddenly the Activity Streams are always empty. It is very annoying for the users who were very dependent on them. So I need to get the activity streams back.
What I have tried so far:
1. Reindexing
2. Creating a new widget for activity stream
What log can I look into to see what is broken? Do I need to create a new filter or something?
Please do not create activitystream-gadget.xml. Instead, remove the gadgets you have now and install the latest versions of each--including the Activity Stream gadget itself.
Please look at your atlassian-jira.log file.
Mostly this is caused by outdated plugins using deprecated (and now removed) classes. Similar thing happened to me when OSUser class was removed due to deprecation and an older plugin still used it.
If you are not able to view the log, try disabling user installed plugins.

TinyMCE upgrade an modified editor to the latest version mayhem

It is this sad moment to a developer's life that he has to maintain and fix legacy code... In my case I have to deal with a modified (core scripts) tinyMCE 3.2.2 which I have to update to the latest version in order to play in IE9+...
So my question is if there is a way to check which files have been changed since version 3.2.2 and try to update only those cause it is an overkill to check all the code for the modifications...
Thanks in advance
I fear there are so many changes in so many files that most of them have changed since then and in order to work with IE9.
If possible you should never ever modify the core code. Instead use custom plugins if possible.