Logging batteris for effect-ts
No description provided.
The missing standard library for TypeScript, for writing production-grade software.
A wrapper package that uses `useInsertionEffect` or a fallback for it
Ponyfill of the experimental `React.useEffectEvent` hook
A React helper hook for scheduling a layout effect with a fallback to a regular effect for environments where layout effects should not be used (such as server-side rendering).
A SQL toolkit for Effect
It's react's useEffect hook, except using deep comparison on the inputs, not reference equality
Create components whose prop changes map to a global side effect
Unified interfaces for common platform-specific services
Create components whose prop changes map to a global side effect
Platform specific implementations for the Node.js runtime
Functional programming in TypeScript
A React hook that uses useEffect() on the server and useLayoutEffect() in the browser
Experimental modules for the Effect ecosystem
An easy to use, extensible pretty-printer for rendering documents for the terminal
A set of helpers for testing Effects with vitest
ESLint rule to warn against unnecessary React useEffect hooks.
OpenTelemetry integration for Effect
A Quick description of the component
Effectful AWS Lambda Powertools Logger
👻🔁
A Quick description of the component
A Quick description of the component
Effect-logging service (forwards to tracing) for effect! / AsyncEffect programs
Effect-logging service (forwards to tracing) for effect! / AsyncEffect programs
Use this library effectively log different data types
Pipe a file, like a log file, into text_to_noise and it will play sound effects triggered by regex matches in the input.
Dekiru::DataMigration provides features for data migration tasks including progress display, transaction management, execution confirmation, side effect monitoring, and detailed logging.
The Soft Assert gem enhances testing capabilities with flexible assertion methods.Unlike traditional assertions, Soft Assert does not interrupt test execution on failure. Instead, it logs errors and continues testing, allowing you to identify and review all failures simultaneously. This gem integrates smoothly with leading testing frameworks, including Minitest and Test::Unit, making comprehensive testing more efficient. To utilize Soft Assert effectively, simply use its assertion methods during testing. Then, conclude with SoftAssert.assert_all to review and fail the test if any failures were captured.
Enhance your Rails application’s communication capabilities with Communify, a robust gem designed to seamlessly integrate SMS, push notifications, and email logging. Leveraging the power of Twilio and Firebase Cloud Messaging, Communify enables developers to effortlessly send important alerts and updates while maintaining comprehensive logs of all communications. With its straightforward implementation, Communify simplifies your messaging infrastructure, allowing you to focus on delivering exceptional user experiences. Ideal for developers seeking a unified solution for effective customer engagement.
This Devise extension adds the ability for users to authenticate with one-time passwords, enabling a more secure session mechanism. When logging in, users will receive a unique one-time password that they can use to access the system. This password is valid for only one use, ensuring that each login is secure and that users cannot reuse an old password to access their account. This extension provides a simple and effective way to improve the security of your application and protect against password attacks.
== Devise::Revokable A module for Devise[http://github.com/plataformatec/devise] This gem was created by "borrowing" heavily from Devise::Invitable[http://github.com/scambra/devise_invitable] It exists to extend Devise to provide the basis for what is essentially the reverse of the standard <tt>confirmable</tt> module. Where <tt>confirmable</tt> sends an email and awaits a response, before confirming a new registration, <tt>revokable</tt> allows immediate access and sends an email which provides a link to "revoke" the account if it was created fraudulently. This is useful if you want to lower the barrier to entry to creating accounts, and clearly, if account security isn't a concern. Note that tests are non-existent. Use freely but at your own risk. === Configuring It works like normal Devise modules. Add the <tt>:revokable</tt> module to the declaration. # in user.rb devise :revokable # plus other devise modules If the user who received the revocation email follows the provided link and confirms revocation, the account will effectively be "revoked" and inactive, unable to log in. Additionally, you may want to override <tt>#revoke!</tt> to perfom additional revocation on the account, e.g. deleting posts made, resetting personal information, etc. The super method yields to a block for this purpose. # in user.rb def revoke! super do self.some_method_that_resets_me! end end That's about the extent of it. As with typical devise modules you can override the mailers and views with your own. Additionally you can define the module accessor <tt>@@mailer</tt> on the module with a proc to handle your mail if you need to. This proc is yielded two arguments, the method name (e.g. :revocation_instructions), and the affected resource. # in config/initializers/devise_revokable.rb require 'devise_revokable' require 'my_mailer' DeviseRevokable.mailer = proc {|method_name, resource| MyMailer.send(:method_name, resource) }
Chef-Berksfile-Env ================== A Chef plugin which allows you to lock down your Chef Environment's cookbook versions with a Berksfile. This is effectively the same as doing `berks apply ...` but via `knife environment from file ...`. View the [Change Log](https://github.com/bbaugher/chef-berksfile-env/blob/master/CHANGELOG.md) to see what has changed. Installation ------------ /opt/chef/embedded/bin/gem install chef-berksfile-env Usage ----- In your chef repo create a Berksfile next to your Chef environment file like this, chef-repo/environments/[ENV_NAME]/Berksfile This is the default location that will used by the plugin. We have to put the Berksfile in its own directory since [multiple Berksfiles can't exist in the same directory](https://github.com/berkshelf/berkshelf/issues/1247). The berksfile should include any cookbooks that your nodes or roles explicitly mention for that environment, source "https://supermarket.getchef.com" cookbook "java" cookbook "yum", "~> 2.0" ... Next we need to generate our Berksfile's lock file, berks install Your environment file must by in `.rb` format and look like this, require 'chef-berksfile-env' # The name must be defined first so we can use it to find the Berksfile name "my_env" # Load Berksfile locked dependencies as my environment's cookbook version contraints load_berksfile ... Now our environment will use the locked versions of the cookbooks and transitive dependencies generated by our Berksfile. Upgrading to the latest dependecies is now as simple as, berks install Our Berksfile also provides an easy way to ensure all the cookbooks and their versions that our environment requires are uploaded to our chef-server, berks upload How the Plugin Finds the Berksfile ---------------------------------- If you are curious how the plugin knows to find the Berksfile in `chef-repo/environments/[ENV]/Berksfile`, you want to put your Berksfile somewhere else or you have run into this error `Expected Berksfile at [/path/../Berksfile] but does not exist`, this section will explain how this works and ways to tweak the path or fix your error. `load_berksfile` has an optional argument which represents the path to your Berksfile. This path can be pseduo relative (explained in a moment) or absolute. By default the value is `environments/[ENV_NAME]/Berksfile`. By pseduo relative I mean that its a relative path but the plugin will check to see if the directory we are executing from partially matches our relative path. So if we are running knife from `/home/chef-repo/environments` and our relative path is `chef-repo/environments/dev/Berksfile` the plugin will see that the relative path is partially included in our execution directory and will attempt to merge the two to come up with `/home/chef-repo/environments/dev/Berksfile`. If we can't make any match at all we attempt to guess the path by just joining the relative path with our execution directory. So why do we do this? Well the only way to use this plugin is if your environment is in Ruby format. Chef's `knife from file ...` uses Ruby's `instance_eval` in order to do this. This means the code on Chef's end effectively looks like this, env.instance_eval(IO.read(env_ruby_file)) which means that any context about the location of the environment file is lost. So we have no great way to discern the location of our environment Ruby file, so instead we guess.
Contentful API wrapper library exposing an ActiveRecord-like interface
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.