rickychien / comiz Goto Github PK

As title

I prefer to use istanbul as code coverage tool and coveralls as online reporter.

URL is still an useful role in SPA to keep application state as URL.

It improves:

• Ability to share a comic link.
• Ability to support bookmark for subpages.
• Re-trigger a fetch error page again by Ctrl / Cmd + R or F5 instead of refresh to landing page.
• Keep browser history.

See also react-router and react-router-redux

To get rid of server side support and simplify deployment configuration, I'm favor of using hash to do router instead.

在首頁時，當頁面滾動到底自動載入未載入的漫畫清單

A fresh idea in my mind would be a top-down scroll pagination which is like a Facebook timeline. It is able to trigger a content refresh if user hits content's top or down boundary.
This feature will involve new UI/UX design that should have more discussion.

Hey guys, I love comiz. Thanks for created this.

I found that the comic page can't not open on my iPhone 6 plus. (iOS 9.3.5)

but the index page is fine.

Any suggestions?

As title, we should add eslint as our coding style sheriff.

I noticed that if you are watching an episode pages and switch to another one, previous pages will remain on screen until new data is fetched completely.
We should display a loading indicator while a new episode pages comes in.

As README.md [1] mentioned, we should conform our application state to this design in order to make react component props more easy to pass through and maintain.

[1] https://github.com/rickychien/comiz#application-state-structure

Hi,
Comiz is my favorite manga reader on Internet. Thanks !
But it was broke from few days ago.
Could you take a look, plz ?

Some comics are scattered at the end of ComicList view and make it feels weird for me. It should fill entire page until it displays rest of comics.

We now introduced a react router that improved history navigation is pretty great. However, navigating history is really awful since it always display same name Comiz wherever you visit. So, we should change title name as we visit different content.

We should restructure our build system including:

1. New dev / prod webpack configurations for switching different build by a flag.
2. A new npm run push command to push production static website to gh-pages easily.

We should save certain of useful user preference data on local such as favorites and reads in order to offer better experience to user.

1. Opened it, and switched to second page.
2. Searched "12"
3. Nothing was displayed except a up arrow which was clickable. And the mangas are shown until I tried to click the arrow.

It will increase performance and provide more explicit and concise state & props comparison. Need to figure out which's the best way [1] [2] to construct application state

[1] https://facebook.github.io/react/docs/update.html
[2] https://facebook.github.io/immutable-js/

Close a drawer by swiping gesture is a very common way for mobile user to control UI component like drawer.

We've already setup build and lint on jobs Travis CI. It would be better if we are able to improve code quality by enabling unit / integration test on CI automatically.

See also remix-run/react-router#1967

I'd like this feature that makes desktop experience more convenient