Taras Mankovski
Taras Mankovski
@monocle your summary is what I discovered after working with EIDB for about 1 day. IMHO, the ceremony that you abstracted in the EIDB interface should be implemented on instance...
Could we open the database every time, here is some pseudo code... ``` javascript Database.prototype = { dbName: null, ... createObjectStore: function(storeName, options) { var createObjectStore = function(db) { //...
> There's some recursion going on that I don't think we could get around. You're probably right, if I can get testing figured out, then maybe I can experiment with...
I believe so. I don't remember. It's been so long :)
Hi @FredKSchott, thank you for taking the time to get back to me. If I understand correctly, the idea is that `@pika/plugin-standard-pkg` will use `.babelrc` to transpile to ES2018 features...
You are correct in that Node should not be transpiling `class` syntax because the default `minNodeVersion` is 6. I had `@babe/preset-env` in my .babelrc which caused everything to get compiled...
Seeing version number in the console would be very nice, but it would only be available in development because production build suppresses debug messages. With contentFor, you the version number...
@lukemelia great idea!
@wKich is working on a workaround and a more permanent solution to this in here https://github.com/thefrontside/interactors/pull/208
@cowboyd I think I didn't know I can get that. I'll try it.