Require that is scoped to directories
Makes localy scoped require to be assigned to window browser object, thus available functionality with selenium.
Babel plugin to ensure function declarations at the block level are block scoped
Check if a string is a scoped npm package name
Regular expression for matching scoped npm package names
Mylas is a npm package to make the loading and storing of data from fs easy and reliable.
ESLint plugin for Scoped CSS in Vue.js
gets the package name for a require statement
Allows to auto define custom elements scoping them
Regular expression for matching npm organization names
Babel plugin to ensure function declarations at the block level are block scoped
Request-scoped storage support, based on Asynchronous Local Storage, with fallback to cls-hooked for older Node versions
Custom, renamable groups for TailwindCSS
Translates between file formats and generates static code as well as TypeScript definitions.
A continuation-local storage module compatible with NestJS's dependency injection.
Zero-runtime Stylesheets-in-TypeScript
Scoped CustomElementRegistry Polyfill
A library for building fast, lightweight web components
Zero-runtime Stylesheets-in-TypeScript
A mixin for using speculative "scoped CustomElementRegistry" with LitElement.
Zero-runtime Stylesheets-in-TypeScript
vite-plugin-istanbul ==========================
Stylelint rule for CSS modules to prevent usage of global-scoped selectors
ShadyCSS scoped element
Map query params to model scopes, pairing one or more keys to a scope. Parameters can be required, or whitelisted providing fine tuned control over how scopes are run.
Access to hiera variables. Requires hiera.yaml and scope defined.
Require by path, Define without key. Permissive towards Sprockets directives and global scope pollution.
Scoped search makes it easy to search your ActiveRecord-based models. It will create a named scope :search_for that can be called with a query string. It will build an SQL query using the provided query string and a definition that specifies on what fields to search. Because the functionality is built on named_scope, the result of the search_for call can be used like any other named_scope, so it can be chained with another scope or combined with will_paginate. Because it uses standard SQL, it does not require any setup, indexers or daemons. This makes scoped_search suitable to quickly add basic search functionality to your application with little hassle. On the other hand, it may not be the best choice if it is going to be used on very large datasets or by a large user base.
ContextualConfig provides a flexible framework for managing configurations that can be applied based on contextual rules, priorities, and scoping. Perfect for complex applications requiring dynamic configuration resolution.
This gem provides an acts_as_list compatible capability for sorting and reordering a number of objects in a list. The class that has this specified needs to have a +position+ column defined as an integer on the mapped database table. This gem requires ActiveRecord 3.0 as it has been refactored to use the scope methods and query interface introduced with Ruby on Rails 3.0
SimpleAuthorize is a lightweight authorization framework for Rails that provides policy-based access control, role management, and scope filtering without requiring external gems. Inspired by Pundit but completely standalone.
scoped_css provides automatic CSS scoping for Rails templates and ViewComponents. It ensures styles are isolated to specific components or templates, preventing CSS conflicts and enabling modular styling. The gem works by automatically adding unique scope identifiers to CSS rules and corresponding HTML elements, making it easy to maintain clean, conflict-free stylesheets in large applications. No CSS preprocessors or postprocessors are required.
## Overview Privileged Access Manager (PAM) is a Google Cloud native, managed solution to secure, manage and audit privileged access while ensuring operational velocity and developer productivity. PAM enables just-in-time, time-bound, approval-based access elevations, and auditing of privileged access elevations and activity. PAM lets you define the rules of who can request access, what they can request access to, and if they should be granted access with or without approvals based on the sensitivity of the access and emergency of the situation. ## Concepts ### Entitlement An entitlement is an eligibility or license that allows specified users (requesters) to request and obtain access to specified resources subject to a set of conditions such as duration, etc. entitlements can be granted to both human and non-human principals. ### Grant A grant is an instance of active usage against the entitlement. A user can place a request for a grant against an entitlement. The request may be forwarded to an approver for their decision. Once approved, the grant is activated, ultimately giving the user access (roles/permissions) on a resource per the criteria specified in entitlement. ### How does PAM work PAM creates and uses a service agent (Google-managed service account) to perform the required IAM policy changes for granting access at a specific resource/access scope. The service agent requires getIAMPolicy and setIAMPolicy permissions at the appropriate (or higher) access scope - Organization/Folder/Project to make policy changes on the resources listed in PAM entitlements. When enabling PAM for a resource scope, the user/ principal performing that action should have the appropriate permissions at that resource scope (resourcemanager.{projects|folders|organizations}.setIamPolicy, resourcemanager.{projects|folders|organizations}.getIamPolicy, and resourcemanager.{projects|folders|organizations}.get) to list and grant the service agent/account the required access to perform IAM policy changes. Note that google-cloud-privileged_access_manager-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-privileged_access_manager instead. See the readme for more details.
## Overview Privileged Access Manager (PAM) is a Google Cloud native, managed solution to secure, manage and audit privileged access while ensuring operational velocity and developer productivity. PAM enables just-in-time, time-bound, approval-based access elevations, and auditing of privileged access elevations and activity. PAM lets you define the rules of who can request access, what they can request access to, and if they should be granted access with or without approvals based on the sensitivity of the access and emergency of the situation. ## Concepts ### Entitlement An entitlement is an eligibility or license that allows specified users (requesters) to request and obtain access to specified resources subject to a set of conditions such as duration, etc. entitlements can be granted to both human and non-human principals. ### Grant A grant is an instance of active usage against the entitlement. A user can place a request for a grant against an entitlement. The request may be forwarded to an approver for their decision. Once approved, the grant is activated, ultimately giving the user access (roles/permissions) on a resource per the criteria specified in entitlement. ### How does PAM work PAM creates and uses a service agent (Google-managed service account) to perform the required IAM policy changes for granting access at a specific resource/access scope. The service agent requires getIAMPolicy and setIAMPolicy permissions at the appropriate (or higher) access scope - Organization/Folder/Project to make policy changes on the resources listed in PAM entitlements. When enabling PAM for a resource scope, the user/ principal performing that action should have the appropriate permissions at that resource scope (resourcemanager.{projects|folders|organizations}.setIamPolicy, resourcemanager.{projects|folders|organizations}.getIamPolicy, and resourcemanager.{projects|folders|organizations}.get) to list and grant the service agent/account the required access to perform IAM policy changes.
Simple REST api for anime.akinyele.ca
The 'pg_search_multiple_highlight' gem extends the functionality of the popular 'pg_search' gem to overcome its limitation when performing searches against multiple columns and attempting to highlight results. The core issue arises when using the ':highlight' option within the ':tsearch' scope on multiple columns. This gem addresses this limitation by introducing the ':multiple_highlight' option, offering a comprehensive solution for highlighting results across multiple columns. Key Features: New Scope Option: The gem introduces the ':multiple_highlight' scope option, allowing users to perform searches on multiple columns and highlight matching terms. Enhanced Search Results: The gem enables the extraction of highlighted results from multiple columns, providing a unified view of highlighted content. Usage Convenience: Users can easily integrate the ':multiple_highlight' option into their existing 'pg_search' queries by calling the '.with_pg_search_multiple_highlight' method on the search object. Flexible Customization: The gem's options can be tailored to match specific highlighting requirements, such as custom start and stop markers for highlighting. Comprehensive Documentation: The README file explains the limitations of 'pg_search' regarding highlighting, demonstrates how the ':multiple_highlight' option resolves this issue, and offers clear usage examples for quick integration.
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.