Backend for the anti Pareto rule
Skins for backend-plus
Capa de aplicación backend-plus para manejo de consistencias en operativos censales
frontend for backend-plus
librería React genérica para consumir backends de tipo backend-plus.
Tester for backend-plus apps
Nuxt plugin for Hasura Backend Plus
Test suite for backend-plus
Nuxt plugin for Hasura Backend Plus
Hasura Backend Plus v2 Nuxt module
Provide customised hasura-backend-plus auth module and users context with hasura connection
Notifications with backend-plus
<p align="center"> <a href="https://github.com/nhost/hasura-backend-plus"> <img src="docs/.vuepress/public/logo.png" width="150px" alt="HBP" /> </a> </p> <h1 align="center">Hasura Backend Plus (HBP)</h1> <h2 align="center">Authentication & Storage
Puntapié inicial para hacer una aplicación en backend-plus desde cero
A JS implementation of JSONPath with some additional operators
Reduce requests to backend services by batching calls and caching records.
rehype plugin to highlight code blocks in HTML with Prism (via refractor) with line highlighting and line numbers
Checkbox with autocomplete and other additions for Inquirer
HTML5 backend for React DnD
i18next-http-backend is a backend layer for i18next using in Node.js, in the browser and for Deno.
A Component Library for Vue 3
Extends the Angular CLI's build process
The Unified Toolchain for the Web
i18next-fs-backend is a backend layer for i18next using in Node.js and for Deno to load translations from the filesystem.
track likes between rails models using Redis backend
This is a fork of Zach Holman's amazing boom. Explanation for the fork follows Zach's intro to boom: God it's about every day where I think to myself, gadzooks, I keep typing *REPETITIVE_BORING_TASK* over and over. Wouldn't it be great if I had something like boom to store all these commonly-used text snippets for me? Then I realized that was a worthless idea since boom hadn't been created yet and I had no idea what that statement meant. At some point I found the code for boom in a dark alleyway and released it under my own name because I wanted to look smart. Explanation for my fork: Zach didn't fancy changing boom a great deal to handle the case of remote and local boom repos. Which is fair enough I believe in simplicity. But I also believe in getting tools to do what you want them to do. So with boom, you can change your storage with a 'boom storage' command, but that's a hassle when you want to share stuff. So kaboom does what boom does plus simplifies maintaining two boom repos. What this means is that you can pipe input between remote and local boom instances. My use case is to have a redis server in our office and be able to share snippets between each other, but to also be able to have personal repos. It's basically something like distributed key-value stores. I imagine some of the things that might be worth thinking about, based on DVC are: Imports/Exports of lists/keys/values between repos. Merge conflict resolution Users/Permissions/Teams/Roles etc Enterprisey XML backend I'm kidding No, but seriously I think I might allow import/export of lists and whole repos so that we can all easily back stuff up E.g. clone the whole shared repo backup your local repo to the central one underneath a namespace
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.