>();\n```\n\n#### Data Manipulation:\n\n- Single or multiple data entries can be stored in the Wapp Storage.\n\n```javascript\n// Set new data into the store\nawait storage.set('key', 'item');\nawait storage.set({ key2: 'item 2', key3: 'item 3' });\n```\n\n- Multiple keys can be retrieved or removed simultaneously, providing efficient data management capabilities.\n\n```javascript\n// Get data from the store\nlet data = storage.get('key');\nlet data2 = storage.get(['key2', 'key3']);\n// Remove data from the store\nawait store.remove('key1');\nawait store.remove(['key2', 'key3']);\n```\n\n#### Features:\n\n- Data can be reloaded from the server using the reload function.\n\n```javascript\n// Reload the data from the server\nawait storage.reload();\n```\n\n- Data can be deleted by using the reset function.\n\n```javascript\n// Delete all the saved data\nawait storage.reset();\n```\n\n- Callbacks can be registered to receive notifications when the storage is updated.\n\n```javascript\n// Signal when storage is changed\nstorage.onChange(() => {\n console.log('Storage is updated');\n});\n```\n\n#### Background Storage:\n\n- Secret information can specifically be stored in the background part of the wapp, ensuring its confidentiality.\n\n- This secret data is exclusively accessible within the background wapp and remains isolated from the frontend part of the application.\n\n```javascript\nawait storage.setSecret('key', 'item');\nconst secret_data = storage.getSecret('key', 'item');\nawait storage.removeSecret('key', 'item');\n```\n\n### OAuth\n\nTo get an already created OAuth token, call the getToken with the name\nof the oauth. If there is no token generated yet, a `Request Handler`\nneeds to be supplied, so that the library can call it with the url\nthat the user needs to visit, in order to generate the OAuth Token.\n\n```javascript\ntry {\n let token = await Wappsto.OAuth.getToken('oauth name', (url) => {\n console.log(`Please visit ${url} to generate the OAuth token`);\n });\n console.log('OAuth Token', token);\n} catch (e) {\n console.log('Failed to get OAuth token', e);\n}\n```\n\n### Notification\n\nIt is possible to send custom notification to the main Wappsto.com\ndashboard.\n\n```javascript\nawait Wappsto.notify('This is a custom notification from my Wapp');\n```\n\nYou can also send an email to your self by calling `sendMail`.\n\n```javascript\nawait Wappsto.sendMail({\n subject: 'Mail with information',\n body: 'Hello from the Wapp
Here is some more information
',\n from: 'My New Wapp',\n});\n```\n\nIt is also possible to send a SMS to your self, if your phone number\nis verified.\n\n```javascript\nawait Wappsto.sendSMS('Simple SMS from your Wapp');\n```\n\n### Ontology\n\nTo build a relationship graph of your data, you need to define the\nontology.\n\nTo add a relationship between two objects, you call `createEdge` with\nthe relationship that you want to define.\n\n```javascript\nconst edge = await startNode.createEdge({ relationship: 'child', to: endNode });\n```\n\nYou can also supply more information about the edge.\n\n```javascript\nconst fullEdge = await startNode.createEdge({\n relationship: 'child',\n to: endNode,\n name: 'My Edge',\n description: 'This is my first edge',\n data: { msg: 'My own data for this edge' },\n});\n```\n\nIf you need a virtual object to create an edge to or from, you can\ncreate a new node. To create a node in the graph, you call the `createNode`\nfunction.\n\n```javascript\nconst startNode = await Wappsto.createNode('start node');\n```\n\nIf you are using TypeScript, you can add a type to the node, like this:\n\n```typescript\ntype CustomNode = {\n name: string;\n age: number;\n};\nconst startNode = await Wappsto.createNode('start node');\n```\n\nIt is also possible to add some data to the node when you create it,\nby supplying it in the constructor.\n\n```javascript\nconst dataNode = await Wappsto.createNode('data node', {\n data: 'my data node',\n});\n```\n\nWhen you have created your ontology, you can `transverse` the graph\nand find 'leafs' in the graph. You need to define a path to\nfollow. There are 3 special characters in the path, that have special\nmeaning. `.` is used to separate each element in the path. `*` is used\nas matching any relationship. `|` is used as an 'or' between relationships.\n\n```javascript\nconst leafs = node.transverse('*.contains|child.*');\n```\n\nWhen calling `transverse` the result is the leaf at the end of the\npath. But if you want all the nodes that are found along the path, you\ncan set 'getAll' to true when calling `transverse`.\n\n```javascript\nconst allNodes = node.transverse('*.contains|child.*', true);\n```\n\nTo load all the ontology edges from an object, you can call `getAllEdges`.\n\n```javascript\nconst edges = await node.getAllEdges();\n```\n\nTo the models that the edge points to is available in the `models` attribute.\n\n```javascript\nedges.forEach((edge) => {\n edge.models.forEach((model) => {\n console.log(`The edge points to ${model.name}`);\n });\n});\n```\n\nThe edges are only loaded once, so if you need to refresh the edges from\nthe backend, you need to force an update by calling `getAllEdges` with true.\n\n```javascript\nconst edges = await node.getAllEdges(true);\n```\n\nIf not all models can be loaded that the edge points to, the failed models are\nstored in `failedModels` on the edge.\n\n```javascript\nconst edges = await node.getAllEdges();\nconsole.log(edges[0].failedModels);\n```\n\nTo remove an edge, you can just call `delete` on the edge, but if you\nwant to remove the whole branch, you can call `deleteBranch`.\nThis will remove all edges and nodes under this node or edge.\n\n```javascript\nawait startNode.deleteBranch();\n```\n\n### Service helpers\n\nThere are a range of helpers avaiable to use in your wapp.\n\n#### UnifyData\n\nUse this helper function to unify data from one value to another.\nThe function takes two `Value` objects and a `LogRequest` as arguments.\nThe first `Value` is the source to read from, while the second is the destination to which the data is sent.\nThe `LogRequest` object controls how the data should be unified.\nAdditionally, there is an optional parameter that allows the data to be converted using a callback function.\n\n```javascript\nunifyData(inputValue, outputValue, { group_by: 'hour', operation: 'max' });\nunifyData(\n inputValue,\n outputValue,\n { group_by: 'hour', operation: 'max' },\n (data) => Number(data) * 2\n);\n```\n\n#### generateHistory\n\nUse this helper function to generate history for a value based on an other values history.\nThe function takes two `Value` objects and a `LogRequest` as arguments.\nThe first `Value` is the source to read the history from,\nwhile the second is the destination to which the history is sent.\nThe `LogRequest` object controls how the log data should be loaded.\nAdditionally, there is an optional parameter that allows the data to be converted using a callback function.\n\n```javascript\nawait generateHistory(inputValue, outputValue, {\n group_by: 'hour',\n operation: 'max',\n});\nawait generateHistory(\n inputValue,\n outputValue,\n {\n group_by: 'hour',\n operation: 'max',\n },\n (data) => Number(data) * 2\n);\n```\n\n### Background logging\n\nThe debug log from the background wapp is enabled by default, but can\nbe turned off by calling `stopLogging`.\n\n```javascript\nWappsto.stopLogging();\n```\n\n### Raw requests\n\nIt is possible to send your own requests to wappsto by using the\n`request` object in wappsto.\n\n```javascript\nlet networks = await Wappsto.request.get('/network');\nawait Wappsto.request.post('/network', { name: 'Network Name' });\n```\n\n### Wapp Version\n\nTo get the current version of the installed application, call `getWappVersion`.\n\n```javascript\nconst version = await Wappsto.getWappVersion();\nconsole.log(`Current Installed Wapp Version: ${version}`);\n```\n\n### Config\n\nIt is possible to change some of the behavior of the library using config.\n\n#### Validation\n\nIt is possible to disable the validation of the input parameters, by\nchanging it in the config. It can be 'none' or 'normal'.\nThe default validation is 'normal'.\n\n```javascript\nWappsto.config({\n validation: 'none',\n});\n```\n\n#### Stream Reconnect Count\n\nIt is possible to change from the default 10 times the stream will try\nto reconnect in case of connection errors.\n\n```javascript\nWappsto.config({\n reconnectCount: 3,\n});\n```\n\n#### Debug information\n\nIt is possible to get a lot of extra debug information about when the\nlibrary is doing by enabling debug options.\n\n```javascript\nWappsto.config({\n debug: true,\n requests: true,\n stream: true,\n});\n```\n","readmeFilename":"README.md"}