webdatarocks v1.4 was released a few days ago
There's no public changelog or post
Anyone knows what changed in this version?
This release was mainly focused on new integration wrappers for Angular, Vue & React. So now it's easier to integrate it via npm.
Also, new predefined skins were added like Striped-Blue, Striped-Teal & Green.
Plus, a few minor fixes were done.
More detailed info can be found here: https://www.webdatarocks.com/blog/webdatarocks-1-4-release-new-long-awaited-features/
Related
So today I was updating one of our SPFX extensions to use the latest spfx framework (1.16) with node (16.13) and after finishing my updates I got the following inside my code:
I am not exactly sure why these are not coming in, I suspect the newest version of spfx moves these classes out of sp-application-base, but why? and where is the documentation for it? Because there is this link that is only 6 months old and explains to use this code for the top and bottom headers.
I was expecting this code to remain in sp-application-base, but it appears it isn't in that package.
How did you perform the upgrade? I highly recommend using the Microsoft 365 CLI to upgrade projects, as the developers of that app do thier best to cover every part of the project that needs to change. Learn more at https://pnp.github.io/cli-microsoft365/cmd/spfx/project/project-upgrade/
Here are the commands to run from the root of your project
npm install -g #pnp/cli-microsoft365
m365 spfx project upgrade --output text
This will give a list of npm commands and code update instructions to follow. See the above documentation for other options for output and use whatever works best for you.
It is still there. What version of #microsoft/sp-application-base is in your project? Should be 1.16.1 I believe. I will say that I am new to all of this as well, but I am using the latest framework and VS is not flagging any issues with these.
I'm following the official tutorial to update a theme from 7.0 to 7.2 https://help.liferay.com/hc/es/articles/360029316831-Running-the-Upgrade-Task-for-7-0-Themes, the process is successful but I need to update to liferay 7.4 and I can't find official documentation or information on how to continue from here, I try to deploy the war on my local server with 7.4 but it says which is not compatible with this version of Liferay. Can someone guide me?
There are 5 years between Liferay 7.0 and 7.4 - and a lot has changed in the frontend world. I'd suggest you either just create a new theme, or (better) check if just using a stylebook with a stock theme is sufficient. A stylebook should be a lot easier to migrate to future versions than a full theme.
I believe that it's technically possible to upgrade a theme, but wouldn't bother doing so. As you have an existing theme, it should be relatively quick to get to where you need to be - plus you'll have the opportunity to make those little adjustments that you likely had an eye on for the past couple of years.
Is there a manual describing migration from Bot Builder SDK v3 to v4?
I have a lot of compilation errors after updating NuGet packages
Update
It appeared to be difficult. In addition to the answer below, I found this post quite useful to get a general picture https://blogs.msdn.microsoft.com/martinkearn/2018/07/17/bot-framework-v4-what-i-learnt-in-4-days-in-july-2018/
You can't just update your NuGet packages from V3 to V4, without changing your code. It is a major release with a lot of breaking changes.
The roadmap
for botbuilder-dotnet describes that a migration path from V3 to V4 is still in progress. I would suggest to have a look at BotBuilder-Samples and Microsoft Docs for the moment, to get an idea about how much has changed.
There are lot of changes from V3 to V4, they have completely re-written the concepts, architecture and terminologies.
So just updating the libraries won't work, you must update the code as well.
The roll-out is still not complete so it is recommended to use v3 in production as of now.
Upgrade is almost equal to the efforts of writing the complete bot code again. In case you are comfortable with your existing bot functionality and is willing to add new features which has nothing to do with SDK version, you can do this using Bot Channel Registration. Steps to do this is mentioned in a blog here - https://chatbotslife.com/microsoft-bot-framework-sdk-3-code-on-azure-bot-service-without-migrating-to-sdk-4-14afa3300887
im currently working on an update from laravel 4.1.24 to 5.6 The problem is i got nearly no experience with laravel. My question is now, how do i properly upgrade. Should i first upgrade to 4.2 and then to 5.0 and so on or would it be better to upgrade directly to 5.6 and how should i do this? I mean there are so many changes that i think i could miss something.
Also the project is just in a github repository, so it's hard to check if it's still working after an upgrade because i dont got the old modules. Or would it be enough to go on laravelshift. com and just upload it there to go from 4.1 to 4.2, 4.2 to 5.0 and so on.
Best regards!
The Laravel documentation contains a whole list of breaking changes that can help you to upgrade your application to a newer version. Laravel Shift is a service that checks and updates these changes in your project.
However, there is no way of being sure that your project will still work after these upgrades. Especially if you are using external modules its very risky.
If it is not required, I would not recommend upgrading from 4.1.x to 5.6 unless you have a lot of time on your hands. A solution could be to set up a completely new 5.6 project and add the project code file by file and test the implementations.
Start from here and follow instructions to upgrade it to 4.2. Then go through your packages and update their versions accordingly. When done use dropdown list in the top-right corner to select next version (5.0) and repeat it until you are at 5.6.
You definitely need to be able to run your code and test it somehow after each step because there will be problems. From 4.1 to 5.6 is a big leap and a lot of packages might have breaking changes etc. I only migrated as far as from 5.1 to 5.6 and it took me whole day to fix everything.
As for automated upgrade you can try it as well, but as I already mentioned you need to be able to test your work because all packages need to be updated as well.
I know some people are using it (PyroCMS) but is CodeIgniter 3.0 complete and ready to be used in production?
I have been using CodeIgniter for many years and although I know it seems to be languishing at the moment it is just so easy to use.
UPDATE: The title of this question used to be "Is CodeIgniter 3 finished?". By this, I meant, is CodeIgniter complete and ready to use in production (not is it dead).
Update:
Version 3 completed on March 30, 2015. See CodeIgniter - Change Log
Original Reply:
No, it's not finished. When it is - you'll see the release announcement on the EllisLab website.
Contrary to what is said in the comments though, this doesn't depend on the issues pending on github and it's not dead either.
Codeigniter is now owned by the British Columbia Institute of Technology.
As of January 26, 2015, the Codeigniter 3.0rc release candidate, its documentation, and relevant changelogs are availble here.
Codeigniter 3.0.1 is now fully compeleted.
you can see changelog here:
http://www.codeigniter.com/userguide3/changelog.html
and Codeigniter 3.1 is in development!!!
Codeigniter has now released 3.0 Candidate version
http://www.codeigniter.com/download
CodeIgniter 3.x is the branch under active development.
A few issues remain to be resolved, and it will not be released until those are put to bed. Version 3 is almost ready for prime time, and many sites are actually using it in production already.
angularjs routing is enabled.