Fork me on GitHub
#perun
<
2016-02-23
>
juhoteperi15:02:30

Hmm, trying to understand what happened with atom and rss tasks.

juhoteperi15:02:01

those names are specified in the spec

juhoteperi15:02:54

Also, atom task is currently creating invalid content (https://t.co/6OAfa1EhJq), I'll fix that but first I need to get those options fixed

adamfrey15:02:35

ok, I didn’t see the SPEC file. I just knew that the options specified by the task were not being passed to the feed generating code, so the rss and atom-feed tasks were unusable

juhoteperi15:02:13

Hmm, I think the correct way forward is to revert patch, fix the task options and rename site-description to description as that is what spec defines

adamfrey15:02:26

yeah, that’s sounds ok to me

juhoteperi15:02:56

Hmm, fixing Atom feed properly needs real UUID:s for each post.

juhoteperi15:02:48

We could have a UUID task which prints a warning and suggestion for UUID so user can add the uuid to entry metadata: "Found a entry x.md without uuid, please add following to the metadata: uuid: 1d04f707-4ec9-4a66-9d74-62c739550106"

juhoteperi15:02:13

We should probably have pre-conditions/assertions/schema specs for properties defined in spec, but not sure if this should be separate task, or if that should be done everywhere the property is used (e.g. base-url)

juhoteperi15:02:33

If the assertion is checked each time, it should only still be printed once per line for e.g. base-url

juhoteperi16:02:47

Still few things to implement, but this should output valid Atom feed: https://github.com/hashobject/perun/pull/92