@libreform/libreform - npm Package Compare versions

Comparing version 2.0.0-beta.13 to 2.0.0

package.json

 {
   "name": "@libreform/libreform",
-  "version": "2.0.0-beta.13",
+  "version": "2.0.0",
   "description": "WP Libre Form client",
@@ -5,0 +5,0 @@ "main": "dist/wplf-frontend",

README.md

@@ -10,3 +10,3 @@ # WP Libre Form
 
-[The older 1.5 branch](https://github.com/libreform/wp-libre-form) is not maintained anymore, and will not receive any updates.
+[The older 1.5 branch](https://github.com/libreform/wp-libre-form) is not maintained anymore, and will not receive any updates, unless someone steps up to do so. Wouldn't recommend it though.
 
@@ -51,5 +51,5 @@ ## Features
 
-The plugin has been rewritten from the ground up, breaking backwards compatibility. In other words; WPLF 1.5 is dead, long live WPLF 1.5!
+The plugin has been rewritten from the ground up, breaking backwards compatibility. In other words; WPLF 1.5 is dead, long live WPLF 2.0!
 
-Nothing in particular was wrong with 1.5, but it was getting a little annoying to maintain. The original version was written during ONE WordCamp, and we had added countless new features since that. You can still use the old version, but it will not receive updates anymore.
+Nothing in particular was wrong with 1.5, but it was getting a little annoying to maintain. The original version was written during ONE WordCamp, and we had added countless new features since that. You can still use the old version, it works as long as WordPress doesn't break backwards compatibility.
 
@@ -101,6 +101,12 @@ As migrations tend to be a pain in the ass, we've made special efforts to ensure that you don't have to migrate. The new version works side by side with the old one. Everything has been renamed so they do not conflict with each other.
 
-### The Old Fashioned Way
+### WordPress.org?
 
-~~This plugin is available on the [official WordPress.org plugin directory](https://wordpress.org/plugins/libre-form/).~~ 2.0 has not been submitted to the wp.org plugin directory yet.
+This plugin will not be released on wordpress.org. During the review process, instead of actually reviewing the plugin, Plugin Review Team just wasted my time. They kept arguing that we need to merge the two codebases together and "provide an upgrade" path, despite 2.0 being entirely backwards incompatible. They do not understand how never breaking backwards compatibility is harmful. Can't blame them, 15 years of legacy would turn anyone's brain into soup.
 
-You can also install the plugin by directly uploading a copy of this repository in your plugins folder.
+I told them that the plugins are fundamentally different, we have different PHP & browser requirements, etc. Doing what they required would've taken WEEKS for no benefit whatsoever.
+
+The opposite actually. The likelihood of end users updating blindly to 2.0 and breaking literally every form they have is too damn high. Writing migrations takes time, and for what benefit? We do not make any money from this, but you as an enduser hopefully do. The time it takes you to manually migrate 10 forms is most likely billable time, and shouldn't take more than a minute per form.
+
+You can run 1.5 and 2.0 side by side without any issues. That wouldn't be possible with their demands. Instead, every form would have to be migrated, writing migrations would take an absurd amount of time, and there would be no guarantee of them working, considering the "just hack around it" mentality in 1.5.
+
+So, if you don't want to use Composer to manage the plugin, download the latest release from GitHub. There are plans to integrate an update mechanism to the plugin, but no timeline for that has been established yet. Contributions are welcome.

.vscode/launch.json

-{
-  "version": "0.2.0",
-  "configurations": [
-    {
-      "name": "Listen for XDebug",
-      "type": "php",
-      "request": "launch",
-      "port": 9000,
-      "log": true,
-      "pathMappings": {
-        "/app/web/wp-content/plugins/wp-libre-form": "${workspaceFolder}/"
-      }
-    }
-  ]
-}

.vscode/settings.json

-{
-  "vscode-php-cs-fixer.toolPath": "/home/k1sul1/Projects/libreform.local/htdocs/wp-content/plugins/wp-libreform/vendor/bin/phpcs",
-  "vscode-php-cs-fixer.config": "/home/k1sul1/Projects/libreform.local/htdocs/wp-content/plugins/wp-libreform/phpcs.xml"
-}

Fixed alerts

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Improved metrics

Total package byte prevSize

638116

0.13%

Number of low quality alerts

3

-25%

Number of lines in readme file

110

5.77%

Worsened metrics

Number of package files

38

-11.63%

Lines of code

8788

-0.05%

No dependency changes