@linked-db/linked-ql - npm Package Compare versions

Comparing version 0.7.0 to 0.7.1

package.json

@@ -14,3 +14,3 @@ {
   "icon": "https://webqit.io/icon.svg",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "license": "MIT",
@@ -17,0 +17,0 @@ "repository": {

README.md

@@ -431,3 +431,3 @@ # Linked QL
 
-3. Have your schemas defined in a `schema.json` file in that directory. (See [`schema.json`](#schemajson) above for a guide.)
+3. Have your DB structure defined in a `schema.json` file in that directory. (See [`schema.json`](#schemajson) above for a guide.)
 
@@ -443,3 +443,3 @@ You can always extend your schema with new objects, and you can always drop objects or edit them in-place. For an existing database, table, column, constraint, or index, **names may be changed, but not in-place!** A "rename" operation is done with the addition of a temporary `$name` attribute:
 
-    The old name in place is needed to find the target during migration. The temporary `$name` attribute automatically disappears after migration.
+    The old name being in place is needed to find the target during migration. The temporary `$name` attribute automatically disappears after new name has been picked up by Linked QL at next `linkedql migrate`.
 
@@ -446,0 +446,0 @@ To run:

Fixed alerts

Major refactor

Supply chain risk

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

1653859

Number of medium supply chain risk alerts

0

decreased by-100%

No dependency changes