@quenty/datastore - npm Package Compare versions

src/Server/Modules/DataStoreSnapshotUtils.lua

test/default.project.json

test/scripts/Client/ClientMain.client.lua

test/scripts/Server/ServerMain.server.lua

CHANGELOG.md

		@@ -6,2 +6,22 @@ # Change Log

		## [7.23.1-canary.402.40f9a1f.0](https://github.com/Quenty/NevermoreEngine/compare/@quenty/datastore@7.23.0...@quenty/datastore@7.23.1-canary.402.40f9a1f.0) (2023-08-16)


		### Bug Fixes

		* Fix additional components but data store writing ping-pings back and forth ([667015d](https://github.com/Quenty/NevermoreEngine/commit/667015d65fe44856076346394c4b218bead012b5))
		* More data store improvements ([b4c5918](https://github.com/Quenty/NevermoreEngine/commit/b4c5918055ffde9e3c5041e98432a13f4e8c913a))


		### Features

		* DataStores appear to be working, but require more testing ([ef03495](https://github.com/Quenty/NevermoreEngine/commit/ef0349554ea29f1812e39bb4bc833adc09c92968))
		* More untested datastore syncing code ([276909d](https://github.com/Quenty/NevermoreEngine/commit/276909dadc819e07b78727d56c95b597760fcf6e))
		* Semi-broken datastore changes ([7e9a32b](https://github.com/Quenty/NevermoreEngine/commit/7e9a32bbadebd729305f36bba965d2c47b14d6d9))
		* Unfinished datastore changes ([d627fa0](https://github.com/Quenty/NevermoreEngine/commit/d627fa0a36f2a733deead8b63b1b72be4e1c3a9f))





		# [7.23.0](https://github.com/Quenty/NevermoreEngine/compare/@quenty/datastore@7.22.0...@quenty/datastore@7.23.0) (2023-08-01)
		@@ -8,0 +28,0 @@

package.json

		{
		"name": "@quenty/datastore",
		"version": "7.23.0",
		"version": "7.23.1-canary.402.40f9a1f.0",
		"description": "Quenty's Datastore implementation for Roblox",
		@@ -29,11 +29,14 @@ "keywords": [
		"dependencies": {
		"@quenty/baseobject": "^6.2.1",
		"@quenty/bindtocloseservice": "^2.18.0",
		"@quenty/loader": "^6.2.1",
		"@quenty/maid": "^2.5.0",
		"@quenty/promise": "^6.7.0",
		"@quenty/rx": "^7.14.0",
		"@quenty/signal": "^2.4.0",
		"@quenty/symbol": "^2.2.0",
		"@quenty/table": "^3.2.0"
		"@quenty/baseobject": "6.2.2-canary.402.40f9a1f.0",
		"@quenty/bindtocloseservice": "2.18.1-canary.402.40f9a1f.0",
		"@quenty/loader": "6.2.2-canary.402.40f9a1f.0",
		"@quenty/maid": "2.5.0",
		"@quenty/math": "2.4.1-canary.402.40f9a1f.0",
		"@quenty/promise": "6.7.1-canary.402.40f9a1f.0",
		"@quenty/rx": "7.14.1-canary.402.40f9a1f.0",
		"@quenty/servicebag": "6.8.1-canary.402.40f9a1f.0",
		"@quenty/signal": "2.4.0",
		"@quenty/symbol": "2.2.0",
		"@quenty/table": "3.2.1-canary.402.40f9a1f.0",
		"@quenty/valueobject": "7.21.1-canary.402.40f9a1f.0"
		},
		@@ -43,3 +46,3 @@ "publishConfig": {
		},
		"gitHead": "839b4d929e4d6154aadf719f1ecfb9add4c8b247"
		"gitHead": "40f9a1fad543e137f1e639cafc45a98cb439b0b6"
		}

README.md

		@@ -18,2 +18,13 @@ ## DataStore

		## Executive overiew
		This datastore prevents data loss by being explicit about what we're writing to, and only modifying the data that exists there instead of modifying the whole structure.

		## How syncing works
		Sometimes datastores (like a global game data store) need to be synced live instead of upon server or player start. This is if we expect multiple servers to write to the same datastore at once we can use thie sync method to

		Syncing is like saving. However, instead of treating the current datastore as a session lock, we load in additional data from our "source-of-truth". From here, we merge that data into the datastore, which means both clearing any matching write tokens that our sync says is done.

		This is best for a "shared" memory that can be temporarily not correct. Deleting with a sync is less effective.


		## Installation
		@@ -20,0 +31,0 @@ ```

src/Server/DataStore.lua