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

Add config option on whether to enable Jekyll output. #17

Closed
wants to merge 1 commit into from

Conversation

rht
Copy link
Contributor

@rht rht commented Dec 14, 2019

This fixes #12.

@@ -141,7 +146,8 @@ def write_stream_index(streams):
sanitize_stream(s, streams[s]['id']),
num_topics,
'' if num_topics == 1 else 's'))
outfile.write('\n{% include ' + str(last_updated_file) + ' %}')
if jekyll_output:
outfile.write('\n{% include ' + str(last_updated_file) + ' %}')
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Mark-Simulacrum what you want is for the {%include ... %} directive to be removed, right? Do you still want the last_updated_file info be in the output somehow?

write_topic_body(messages, stream_name, stream['id'], topic_name, o)
o.write('\n{% endraw %}\n')
o.write('\n{% include ' + str(last_updated_file) + ' %}')
if jekyll_output:
Copy link
Contributor Author

Choose a reason for hiding this comment

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

@Mark-Simulacrum is this what you wanted?

Choose a reason for hiding this comment

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

I would prefer that in non-Jekyll mode we literally include the contents instead of via an include statement. That does mean that all of the files will change on each run, but that's true if you render through jekyll to a static site anyway.

@showell
Copy link
Contributor

showell commented Dec 18, 2019

I am gonna close this PR, since #19 is on the way to address the things that are fixed here.

First, #19 fixes one of the biggest complaints from #12, which is that we had the "include" directive, which was pretty silly in the first place for our use case. (It was literally just importing a one-line date that was easier programmatically to just write to the files directly.)

I'm also doing some structural changes to the overall code that are probably gonna mess with the changes here, but I can crib off of this PR once that settles.

I'm gonna keep #12 open, since we also want to deal with other non-Jekyll scenarios.

@showell showell closed this Dec 18, 2019
@rht rht deleted the include branch December 18, 2019 16:44
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.

Remove Jekyll-specific directives from the markdown output
3 participants