Skip to content
New issue

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

Feature: Optional (packaged) mixins #220

Open
6 tasks
peol opened this issue Aug 25, 2017 · 3 comments
Open
6 tasks

Feature: Optional (packaged) mixins #220

peol opened this issue Aug 25, 2017 · 3 comments

Comments

@peol
Copy link
Contributor

peol commented Aug 25, 2017

This is an idea we've been bouncing around internally for a while. The idea is that we deliver a npm package containing generally useful mixins that may be needed in many use cases. Below I'll outline some of the ones I've identified and suggest this package would contain.

Ideas/feedback welcome!

@konne
Copy link

konne commented Sep 26, 2017

@peol I really like the idea of mixins, but please separate this in two different packages:

  1. helpers (Naming, Doc/Global in API,...)
  2. caching, garbage collection
    I really like the concept of the pure enigmaJS and we always do the caching in our code, because than we have 100% control

@konne
Copy link

konne commented Sep 26, 2017

@peol for the topic naming:
I really prefer if qlik would change the api of the engine and this mixings could be the backward compatible option, to don't break existing extensions,...

@peol
Copy link
Contributor Author

peol commented Sep 26, 2017

thanks @konne — the idea here is that these mixins are provided in an opt-in manner. It's not all or none so it's up to you what you want to use :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants