-
-
Notifications
You must be signed in to change notification settings - Fork 158
Fixed blog order #147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v2
Are you sure you want to change the base?
Fixed blog order #147
Conversation
Deploy preview for nativescript-vue ready! Built with commit 9f5386a |
@rigor789 Can you take a look? |
@ikoevska just checked but I'm not sure if this solves the problem (which seems to only happen sometimes), from a quick test const t = "2018-02-12-nativescript-vue-1.0-and-a-new-site.md"
const a = t.match(/^(\d+)-/)
const b = t.match(/^((\d+)-)+/)
console.log(a[1]) // 2018
console.log(b[1]) // 12- I don't think the order will be accurate when it's set to Maybe we could convert the date to a timestamp, which can then be sorted/ordered |
Weird. I'll get back to the drawing board :D |
Hey @rigor789 second attempt :) This time it seems like it would work. Turned out res[0] is what got the right match that we needed. I am stripping the hyphens from it and passing it along.
|
Use non-capturing groups because we don't need to manipulate the groups separately
This looks good - and I think it should be working, but for some reason the order is still wrong in the build :/ https://deploy-preview-147--nativescript-vue.netlify.com/blog/using-fonticons/ (April 07) I can dig a little deeper next week, don't waste any more time on this - could be a bug in |
Oh, well, I'm still interested in making this one work but I'll be abandoning it for now. |
What I did:
Attempts to solve: #55