https://github.com/fschaeffler/meteor-execution-cache

https://github.com/fschaeffler/meteor-execution-cache

Last synced: 25 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/fschaeffler/meteor-execution-cache
• Owner: fschaeffler
• Created: 2019-08-23T11:44:44.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2022-12-09T23:46:39.000Z (about 2 years ago)
• Last Synced: 2024-12-23T20:24:24.164Z (29 days ago)
• Language: JavaScript
• Size: 313 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 8
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Meteor-Plugin: fschaeffler:execution-cache

## Purpose

This plugin helps with caching per one single execution, where different threads should not have access to the same content. Imagine an export-functionality within an application. You first want to retrieve all data in one bulk and then do the actual data transformation. If your data in your database is normalized, you have references within your data. In order to retrieve such references only once, this cache can get used.

**Data-Example:**

_Table: Users_

| ID  | First Name | Last Name |

| --- | ---------- | --------- |

| 1   | Charlie    | Root      |

| 2   | Foo        | Bar       |

_Table: Content_

| ID  | Content              | UserID |

| --- | -------------------- | ------ |

| 1   | This is some content | 2      |

| 2   | Another content      | 1      |

| 3   | Some more content    | 1      |

_Export: User Content_

| ID  | Content              | User First Name | User Last Name |

| --- | -------------------- | --------------- | -------------- |

| 1   | This is some content | Foo             | Bar            |

| 2   | Another content      | Charlie         | Root           |

| 3   | Some more content    | Charlie         | Root           |

For the export of _User Content_, we not only need the user's ID, but acutal values from the users-table.

## Installation

In order to use this plugin with a Meteor-application, just install it as a package via `meteor add fschaeffler:execution-cache`.

## Tests

-   code style: `npm run prettier`

-   JavaScript best practices: `npm run eslint`

-   unit tests: `npm run tests`

## package.js vs package.json

This package is a Meteor-package, which means the file `package.js` is getting used as entry point. However, for development-purposes, also NPM-dependencies and scripts are needed. Therefore, also a `package.json` is available.