Libraries tagged by parameter
phptramp/phptramp
4356 Downloads
Static analyzer that detects tramp data: parameters passed through chains of PHP methods that never use them.
naugrim/laravel-sentry-tunnel
67130 Downloads
Provides an endpoint to use the `tunnel`-parameter of the Sentry SDK
nandi95/laravel-env-in-aws-ssm
4029 Downloads
Manage your environment variables in AWS' SSM Parameter store
mdaliyan/farsi-request
876 Downloads
A (Laravel Request Transformer) that replaces Arabic characters with Farsi characters, and auto-converts numbers in parameters that you want.
marshmallow/marketing-data-tracker
2663 Downloads
Parse and store marketing parameters like gclid, utm_*, and adid, and automatically attach them to user conversions or models in Laravel.
markocupic/contao-bundle-creator-bundle
5119 Downloads
This bundle provides a bundle maker for Contao 5.3 and Contao 6. The extension will create a fully working backend- or/and frontend module after you have defined a few parameters in the Contao backend.
lincanbin/php-pdo-mysql-class
6891 Downloads
A PHP MySQL PDO class similar to the Python MySQLdb, which supports iterator and parameter binding when using 'WHERE IN' statement.
johannesschobel/dingoquerymapper
26894 Downloads
Uses Dingo/API Request Query Parameters to filter Laravel Models
inda-hr/php_sdk
1445 Downloads
# Introduction **INDA (INtelligent Data Analysis)** is an [Intervieweb](https://www.intervieweb.it/hrm/) AI solution provided as a RESTful API. The INDA pricing model is *credits-based*, which means that a certain number of credits is associated to each API request. Hence, users have to purchase a certain amount of credits (established according to their needs) which will be reduced at each API call. INDA accepts and processes a user's request only if their credits quota is grater than - or, at least, equal to - the number of credits required by that request. To obtain further details on the pricing, please visit our [site](https://inda.ai) or contact us. INDA HR embraces a wide range of functionalities to manage the main elements of a recruitment process: + [**candidate**](https://api.inda.ai/hr/docs/v2/#tag/Resume-Management) (hereafter also referred to as **resume** or **applicant**), or rather a person looking for a job; + [**job advertisement**](https://api.inda.ai/hr/docs/v2/#tag/JobAd-Management) (hereafter also referred to as **job ad**), which is a document that collects all the main information and details about a job vacancy; + [**application**](https://api.inda.ai/hr/docs/v2/#tag/Application-Management), that binds candidates to job ads; it is generated whenever a candidate applies for a job. Each of them has a specific set of methods that grants users the ability to create, read, update and delete the relative documents, plus some special features based on AI approaches (such as *document parsing* or *semantic search*). They can be explored in their respective sections. Data about the listed document types can be enriched by connecting them to other INDA supported entities, such as [**companies**](https://api.inda.ai/hr/docs/v2/#tag/Company-Management) and [**universities**](https://api.inda.ai/hr/docs/v2/#tag/Universities), so that recruiters may get a better and more detailed idea on the candidates' experiences and acquired skills. All the functionalities mentioned above are meant to help recruiters during the talent acquisition process, by exploiting the power of AI systems. Among the advantages a recruiter has by using this kind of systems, tackling the bias problem is surely one of the most relevant. Bias in recruitment is a serious issue that affect both recruiters and candidates, since it may cause wrong hiring decisions. As we care a lot about this problem, we are constantly working on reduce the bias in original data so that INDA results may be as fair as possible. As of now, in order to tackle the bias issue, INDA automatically ignores specific fields (such as name, gender, age and nationality) during the initial processing of each candidate data. Furthermore, we decided to let users collect data of various types, including personal or sensitive details, but we do not allow their usage if it is different from statistical purposes; our aim is to discourage recruiters from focusing on candidates' personal information, and to put their attention on the candidate's skills and abilities. We want to help recruiters to prevent any kind of bias while searching for the most valuable candidates they really need. The following documentation is addressed both to developers, in order to provide all technical details for INDA integration, and to managers, to guide them in the exploration of the implementation possibilities. The host of the API is [https://api.inda.ai/hr/v2/](https://api.inda.ai/hr/v2/). We recommend to check the API version and build (displayed near the documentation title). You can contact us at [email protected] in case of problems, suggestions, or particular needs. The search panel on the left can be used to navigate through the documentation and provides an overview of the API structure. On the right, you can find (*i*) the url of the method, (*ii*) an example of request body (if present), and (*iii*) an example of response for each response code. Finally, in the central section of each API method, you can find (*i*) a general description of the purpose of the method, (*ii*) details on parameters and request body schema (if present), and (*iii*) details on response schema, error models, and error codes.
ianrodrigues/pest-plugin-code-quality
201 Downloads
Method-level and class-level maintainability limits (complexity, body lines, parameters, methods, properties, inheritance depth) as Pest architecture expectations, with baselines for gradual adoption.
hashemi/queryfilter
1333 Downloads
A simple & dynamic package for your eloquent query in laravel. It will help you to write query logic individual for each parameter.
friendsoftypo3/rdct
165742 Downloads
RDCT Frontend redirects - Frontend redirects based on RDCT GET parameter
fdmind/ignore-query-strings
5719 Downloads
If your website has static caching on, and you drive traffic to it from social media, Google Ads and other sources that add query string parameters to the URL, there is a chance that each time new user visits a page, it will not be served from cache, but will be generated from scratch. This is because the URL with query string parameters is treated as a different URL from the one without query string parameters.
emakinafr/magento2-pagecache-bypass
32451 Downloads
A lightweight module to allow bypassing the built-in page cache with an HTTP parameter.
eliashaeussler/typo3-solver
2279 Downloads
Solver - Extends TYPO3's exception handling with AI generated solutions. Problems can also be solved from command line. Several OpenAI parameters are configurable and prompts and solution providers can be customized as desired.