-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
grunt-assemble withSort stops working #64
Comments
@maekke97 Thanks for the issue! If you're reporting a bug, please be sure to include:
|
One thing that I noticed is that in the yaml frontmatter the property is If it was a typo and that's not causing an issue, I'm not exactly sure what might be going on. It would help if you could share the repository or at least a list of all of the pages with their |
Hi, thanks for looking into this. I'm not able to share the repo, as it lies on our privat company server, sorry. $ grunt -V
grunt-cli v1.2.0
grunt v0.4.5
$ npm -v
6.1.0
$ node -v
v8.11.4
$ npm list grunt-assemble
[email protected]
└── [email protected] The project structure:
Gruntfile.js: grunt.initConfig({
assemble: {
options: {
collections: [{
name: 'post',
sortby: 'posted',
sortorder: 'descending'
}],
flatten: true,
partials: ['templates/includes/*.hbs'],
layoutdir: 'templates/layouts',
layout: 'default.hbs'
},
site: {
files: {
'dest/': ['templates/*.hbs','content/news/*.md']
}
}
},
... Grunt assembles all without error. The result with only 9 news blog files can be seen here: http://api.meteomatics.com/ |
Thanks for the additional information, I'll try to look at this soon. |
Hi,
I'm not sure if this is the correct place to post this, please redirect me if I'm wrong.
We have a grunt setup to create our api documentation (http://api.meteomatics.com).
The main content pages have a handlebar header as follows:
Our news blog entries like so:
Then we build our navbar using
#withSort
:(I removed some content to make the example smaller)
This works all fine with up to 41 input pages. As soon as I add the 42nd (The 10th news blog entry), the sorting breaks and the navigation is in alphabetical order.
Does anyone have an Idea, what this could be?
The text was updated successfully, but these errors were encountered: