Skip to content
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

ignore posts which were set as draft in the front-matter #44

Merged
merged 8 commits into from
Apr 24, 2017

Conversation

mamboer
Copy link
Contributor

@mamboer mamboer commented Sep 28, 2016

No description provided.

@coveralls
Copy link

coveralls commented Sep 28, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 4c46820 on mamboer:master into f1977f8 on hexojs:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 0621050 on mamboer:master into f1977f8 on hexojs:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling c89b42b on mamboer:master into f1977f8 on hexojs:master.

atom.xml Outdated
@@ -22,7 +22,7 @@
<published>{{ post.date.toISOString() }}</published>
<updated>{{ post.updated.toISOString() }}</updated>
{% if config.feed.content and post.content %}
<content type="html"><![CDATA[{{ post.content | safe }}]]></content>
<content type="html"><![CDATA[{{ post.content | uriencode }}]]></content>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why need to change this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It sucks when the post's content contains emoji chars like 😀
Use the uriencode filter can resolve this problem.
o2team/o2team.github.io#21

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the clarification.

@NoahDragon
Copy link
Member

LGTM. Could you please fix the jscs error?

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 9f87712 on mamboer:master into f1977f8 on hexojs:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 6316c43 on mamboer:master into f1977f8 on hexojs:master.

package.json Outdated
@@ -1,6 +1,6 @@
{
"name": "hexo-generator-feed",
"version": "1.2.0",
"name": "hexo-generator-xfeed",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I notice the package name has changed. Is it a typo?

package.json Outdated
"hexo": "^3.0.0",
"jscs": "^2.11.0",
"cheerio": "^0.22.0",
"eslint": "^3.19.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest keeping these package in their old version. I assume the CI errors are caused by the new versions.

@coveralls
Copy link

coveralls commented Apr 24, 2017

Coverage Status

Coverage remained the same at 100.0% when pulling fbcd27e on mamboer:master into f1977f8 on hexojs:master.

…int-config-hexo has a dependence on babel-eslint, but our project miss it.
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 906e7b1 on mamboer:master into f1977f8 on hexojs:master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 906e7b1 on mamboer:master into f1977f8 on hexojs:master.

@NoahDragon NoahDragon merged commit 16398e5 into hexojs:master Apr 24, 2017
@NoahDragon
Copy link
Member

Thanks for your contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants