joaomosmann / mospa Goto Github PK

Instead of just using hashes. Also implement the pushState API.

By default it will be the hash history, but passing through the config object of the application the property history_mode a value of pushstate, it will use the pushState Api.

To improve the flexibility of Mospa. It will be necessary a way to set a kind of hash state for a page. Maybe it will be only necessary in the MosScrollApp.

For example. Scrolling the page, I stop at the product section of the SPA. Inside this section, I click some buttons that change the hash, and shows me different products.
At this moment I'm at this hash #/products/category/50/product/10. So, if I scroll out of this section, and come back again, it should back to the hash mentioned before, and not to #/products.

Therefore, my proposal is, that any time a page has a hashchange event triggered to it. It saves the hash state.

At this moment. The location.hash passed to an array by '#/mypage/hash'.split('/');.

But it should be able to customize. So, I could define a Regex to process the hash string into an array.

Something like this.

mospa.createApplication({
...
    hashFormat: /^(?:#)(\/.*\/?)*/      
...
});