summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kitenet.net>2011-01-14 15:05:19 -0400
committerJoey Hess <joey@kitenet.net>2011-01-14 15:05:19 -0400
commitec5c5b8f7ab9e6e263dc85d933f9732dcfc8f9d3 (patch)
tree52230f7c790154e3c75ebbb201d4ccf7b70e8362
parentb9c45e84aa9b162e62af324f5cdb94db984f7358 (diff)
review remaining patches
-rw-r--r--doc/todo/feed_enhancements_for_inline_pages.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/todo/feed_enhancements_for_inline_pages.mdwn b/doc/todo/feed_enhancements_for_inline_pages.mdwn
index 3ca613609..ee28ffa6e 100644
--- a/doc/todo/feed_enhancements_for_inline_pages.mdwn
+++ b/doc/todo/feed_enhancements_for_inline_pages.mdwn
@@ -85,6 +85,27 @@ A few patches to clean up and improve feed management for inline pages.
not squashing it with the second patch to allow you to scrap this but sitll get the other, in case
you're not too happy about having a plethora of parameters
+ > This seems clearly a good idea, since there is already a "description"
+ > parameter. But, by analogy with that parameter, it should just be
+ > called "title". --[[Joey]]
+
* a fifth patch introduces an `id` parameter to allow setting the HTML id attribute in the
blogpost/feedlinks template. Since we replace their id with a class (first patch), this brings
back the possibility for direct CSS customization and JavaScript manipulation based on id.
+
+ > That sort of makes sense, but it somehow seems wrong that "id" should
+ > apply to only cruft at the top of the inline, and not the entire div
+ > generated for it. --[[Joey]]
+
+* 30a4de2aa3ab29dd9397c2edd91676e80bc06feb "urlto: prevent // when {url} ends with /"
+
+ > The `url` in the setup file should not end in a slash. Probably more
+ > things get ugly doubled slashes if someone does that. --[[Joey]]
+
+* 57a9b5c4affda9e855f09a64747e5225d6254079 "inline: use urlto instead of manually building the RSS url"
+
+ > Well, that seems ok. 3 parameter urlto should give us an absolute url.
+ >
+ > But we have to be careful and verify that it will always produce
+ > exactly the same url as before. Changing the feed url unnecessarily
+ > can probably flood aggregators or something... --[[Joey]]