aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorhttp://smcv.pseudorandom.co.uk/ <http://smcv.pseudorandom.co.uk/@web>2010-04-01 01:35:35 +0000
committerJoey Hess <joey@finch.kitenet.net>2010-04-01 01:35:35 +0000
commit63bc057690d388a81e643d4556c6a001d886b59c (patch)
treea031936e5b81c995cde2d17a6b59bbdd1f18e745
parent4eed0abc8c181a027fa802d209fd95d8c10ee9f0 (diff)
downloadikiwiki-63bc057690d388a81e643d4556c6a001d886b59c.tar
ikiwiki-63bc057690d388a81e643d4556c6a001d886b59c.tar.gz
-rw-r--r--doc/plugins/contrib/report/discussion.mdwn7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/plugins/contrib/report/discussion.mdwn b/doc/plugins/contrib/report/discussion.mdwn
index 953509297..a257198c0 100644
--- a/doc/plugins/contrib/report/discussion.mdwn
+++ b/doc/plugins/contrib/report/discussion.mdwn
@@ -60,3 +60,10 @@ to select pages? How does it relate to [[todo/wikitrails]] or
>>> Either that, or somehow combine tagging with fields, such that one could declare a tag, and it would create both a link and a field with a given value. (I've been working on something like that, but it still has bugs).
>>> That way, the test for whether something is tagged would be something like "link(tag/foo) and field(tag foo)".
>>> --K.A.
+
+>>>> I can see that this'd work well for 1:1 relationships like next
+>>>> and previous, but I don't think that'd work for pages with more than
+>>>> one tag - as far as I can see, `field`'s data model is that each
+>>>> page has no more than one value for each field?
+>>>> [[todo/Matching_different_kinds_of_links]] has some thoughts about
+>>>> how it could be implemented, though. --s