Order of posts

[piranna]

Posts are sorted by reverse lexicographical order... so issue 117 is showed after 19 and 17 :-P Issue ID should be identified as a number.

[piranna]

Seems it has magically fixed itself... or it was a problem of cache :-P Closing.

[piranna]

The problem, has appeared again, seems it's related to the localstorage since the new posts are the one that appear at the bootm, so I'll reopen it. @formula1, could you be able to review it?

[formula1]

I believe it is in part associated to

• The initial sort - which is necessary
• When I am appending it to the local storage which should handle the sorting better.
• when I'm calling the template add which which gives the dom no indication of the sorting order
• the actual appending to the dom which only appends.

I'll try to solve this right now as well as add a simple version control system. aka

• server will also send the version number
• if the version number > the users version number, clear the cache

[formula1]

I was able to reproduce the issue with the following

localStorage.setItem("issue-list",
  JSON.stringify(
    JSON.parse(
      localStorage.getItem(
        "issue-list"
      )
    ).slice(1)
  )
);

just fixed it and also realized that there are definietly some issues with the user-provider which I'm about to handle

[formula1]

I fixed the problem from before with auth provider, but a new one showed up, I was attempting to write an encoder from hand but everything is simple in theory...........

I have to go at the moment, but what will end up happening is a complete avoidence of querystring all togethor.

[formula1]

It should be working properly: https://github.com/formula1/NodeOS-Blog

I'm currently in the process of merging with this repo

[piranna]

I'll try to solve this right now as well as add a simple version control system. aka

server will also send the version number
if the version number > the users version number, clear the cache

Could you be able to explain this? GitHub metadata should be enough... isn't it?

[formula1]

Essentially, if we are storing things incorrectly or make changes how we store, I am clearing the cache. It's based off what we are doing more than what github is doing. If github's api changes, we'd likely have to reset the cache. If we make changes, we'd likely have to reset the cache

https://github.com/NodeOS/GitBlog/pull/6/files#diff-8920948fe65b76cfdda1a5fe940b4ce7R2