braintree-paypal-client-config
Advanced tools
Weekly downloads
Readme
Shared configuration between Braintree / PayPal client sdk modules, to allow sharing configuration between integrations and avoiding exposing additional complexity for the integrating party.
This allows the different modules to:
npm install --save braintree-paypal-client-config
As the config setter:
import { set, KEYS } from 'braintree-paypal-client-config';
set(KEYS.ALLOW_FOO, true);
As the config getter:
import { get, KEYS } from 'braintree-paypal-client-config';
if (get(KEYS.ALLOW_FOO)) {
doFoo();
}
get(<key>, [default])
Get the current value for the given key, returns undefined
if unset or default
if specified
set(<key>, <value>)
Set the value under the given key.
get_or_set(<key>, <value>)
Gets the value if it is available, otherwise sets a new value.
on(<key>, <handler>)
Calls the handler
every time the key is set. Good for reading configuration values which may change over time.
LOGGER_SESSION_ID
Specify a shared id to send with logs, to correlate between different modules.
// Set a shared session id or get an existing session id
let sessionID = get_or_set(KEY.LOGGER_SESSION_ID, 'abcdef12345');
PAYPAL_FUNDING_DISALLOW
Specify an array of funding sources to inhibit.
// Disallow paypal from rendering card (credit/debit) butttons
set(KEY.PAYPAL_FUNDING_DISALLOW, [ PAYPAL_FUNDING.CARD ]);
npm run setup
./src
and writing tests in ./tests
npm run build
npm run build
Edit tests in ./test/tests
Run the tests:
npm run test
FAQs
Shared config between PayPal/Braintree.
The npm package braintree-paypal-client-config receives a total of 470 weekly downloads. As such, braintree-paypal-client-config popularity was classified as not popular.
We found that braintree-paypal-client-config demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket installs a Github app to automatically flag issues on every pull request and report the health of your dependencies. Find out what is inside your node modules and prevent malicious activity before you update the dependencies.