Conversation
126f229 to
5d1f8c5
Compare
Codecov Report
@@ Coverage Diff @@
## master #252 +/- ##
==========================================
- Coverage 98.68% 98.51% -0.18%
==========================================
Files 31 38 +7
Lines 381 472 +91
Branches 58 70 +12
==========================================
+ Hits 376 465 +89
- Misses 5 7 +2
Continue to review full report at Codecov.
|
|
@nickbalestra can you check what is making Circle fail? |
|
There is no setup for circle on this branch, he tries to enfer some stuff but I think it make sense that it won't be able to run properly |
matteofigus
left a comment
There was a problem hiding this comment.
Let's rebase to re-test circle? 👍
5d1f8c5 to
a848ad3
Compare
|
Rebased! - Cool, its working pretty nice as actually is correct that the node6 build fails but the node8 pass (still waiting for travis.... ) |
|
All good now :), Out of curiosity I want to see how thing change by checking in the lock file for the cache checksum strategy |
| @@ -0,0 +1,14 @@ | |||
| 'use strict'; | |||
| const es6Renderer = require('express-es6-template-engine'); | |||
There was a problem hiding this comment.
Note: For getting started I went with this , rationale:
- getting up and running quicker,
- nice api: (template can simply use
${prop}, without having to do${model.prop}, good for extendibility - very small code, well tested (the
expressspecific code is very small, so we could think of a fork, in case we want to clean that down in a second step). - allows for some nice thing like precompiling templates (as we do for handlebars), not adding that in in this first iteration but i think is something we might want to explore.
|
@nickbalestra not a big fan of the templating choice. To clarify, I think the view should be something like module.exports = ({ name}) => `<div>${name}</div>`;A couple of pros:
module.exports = vm => {
//code
return `...`;
}
|
|
Just fiddling with some ideas :) but I agree with your points. |
|
Couple of thing I also want achieve with this (still in a wip at the moment).
|
|
@matteofigus This should be now ready to review |
|
PS: Once this get merged, I'll rebase all the other outstanding PRs |
… yarn workspace hoisting changes
022ca31 to
423ae27
Compare
|
@matteofigus is now rebased to master |
matteofigus
left a comment
There was a problem hiding this comment.
can we also remove the yarn.lock?
| 'window.oc = window.oc || {};' + | ||
| 'oc.cmd = oc.cmd || [];' + | ||
| 'oc.cmd.push(function(oc){' + | ||
| 'oc.addStylesToHead(\\'${css}\\');' + |
There was a problem hiding this comment.
should we move to <style> + event to keep this consistent with the React one?
| @@ -0,0 +1,51 @@ | |||
| jasmine.DEFAULT_TIMEOUT_INTERVAL = 50000; | |||
|
|
|||
| jasmine.DEFAULT_TIMEOUT_INTERVAL = 50000; | |||
There was a problem hiding this comment.
why is this timeout here twice?
| @@ -0,0 +1,3 @@ | |||
| jasmine.DEFAULT_TIMEOUT_INTERVAL = 100000; | |||
| test('', () => {}); | |||
| // WIP | |||
There was a problem hiding this comment.
This still needs to be completed?
matteofigus
left a comment
There was a problem hiding this comment.
As discussed, this is looking good but we want to handle the empty CSS scenario (similar to React) for when the CSS is not used.
|
@matteofigus give it a look, In this case was possible to reduce the template even further, let me know what ya think |
| 'window.oc = window.oc || {};' + | ||
| 'oc.cmd = oc.cmd || [];' + | ||
| 'oc.cmd.push(function(oc){' + | ||
| "oc.events.fire(\\'oc:cssDidMount\\', \\'${css}\\');" + |
There was a problem hiding this comment.
${css} this should be outside of that
No description provided.