Sarbbottam Bandyopadhyay

refactor(router): using [email protected]

1

and related changes `Application` now encapsulated in `App.js` `index.js` is just rendering it in `` If desired static htmls can be easily generated. - [x] `npm test` - [x] tested...

Can there be direct links to heading?

2

For example, https://pwa.tips/codelabs/serviceworker#how-to-register to Not sure if that would be possible with client-side rendering but would be nice, since this is documentation.

Write better test and code coverage.

Display notification if desired

4

[growl](https://www.npmjs.com/package/growl) might be useful.

use [chalk](https://github.com/chalk/chalk)

Is there a way to fail the test run if the coverage is below a certain threshold? Is there a way to print the high-level coverage summary after the test...

Could you please update dependencies and make a release? Its fetching quite an old-version of [email protected]

Revert "refactor(scheduling): using requestAnimationFrame instead of afterRender"

5

Reverts linkedin/self-focused#9 [One of the tests in #9](https://github.com/linkedin/self-focused/pull/9/files#diff-af56b796fc2f48eda34b26e8fe00678bR162) had to be wrapped in `requestAnimationFrame` otherwise it would not pass. This eventually resulted in forcing the consumer application to result in...

fix(didRender): force didRender on revisiting same route

1

using a hidden `{{link-to}}` to force re-render fixes #2 --- I noticed, that if there is a `{{link-to}}` component present in the template, the component is re-rendered on visiting the...