We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently default "Options" are intermingled with the library code which makes it awkward for users to override defaults.
https://github.com/kingo55/mojito-js-delivery/blob/9f313bd1ba59f1f8dcb80cc4df41b6b02b08f28c/lib/mojito.js#L4-L14
Might there be a way we could initialise Mojito explicitly? e.g.:
Mojito
// lib code ... Mojito.init({ debug: false, cookieDuration: 7, ... });
Or is the current approach better? I.e. sane defaults hardcoded and users override specific options like:
Mojito.options.excluded = true;
The text was updated successfully, but these errors were encountered:
@kingo55 I think Mojito.init({ options }) is better.
Mojito.init({ options })
Sorry, something went wrong.
No branches or pull requests
Currently default "Options" are intermingled with the library code which makes it awkward for users to override defaults.
https://github.com/kingo55/mojito-js-delivery/blob/9f313bd1ba59f1f8dcb80cc4df41b6b02b08f28c/lib/mojito.js#L4-L14
Might there be a way we could initialise
Mojito
explicitly? e.g.:Or is the current approach better? I.e. sane defaults hardcoded and users override specific options like:
The text was updated successfully, but these errors were encountered: