Some extensions cant handle nowiki tags as input (ie. They dont unstrip
markers before doing their processing). I dont know much about SMW but that
would be my first guess as to why nowiki tags arent working in this context.
Which basically leaves entity encoding as the necessary method.
--
bawolff
On Friday, February 16, 2018, George, Garrett J. (JSC-CB111)[SGT, INC] <
garrett.j.george(a)nasa.gov> wrote:
I don't need any wiki parsing, the template is
really just a way to have
a data model for my extension to use and query using `ask`
queries via
semantic mediawiki.
Reasons it might not be working:
1. AI Comment is a subobject template and something in there is
causing
issues.
2. AI Comment is called within a template and that's causing parse
problems.
This is my template for AI Comment
#
# (1) Create subobject of action item comment
#
-->{{#subobject:
|Comment author={{{Comment author|}}}
|Comment date={{{Comment date|}}}
|Comment text={{{Comment text|}}}
|Comment uuid={{{Comment uuid|}}}
}}<!--
#
# Display comment info in JSON
#
-->
{
"author": "{{{Comment author|}}}",
"date": "{{{Comment date|}}}",
"text": "{{{Comment text|}}}",
"uuid": "{{{Comment uuid|}}}"
}
Because I can't figure out how to properly query for all action items and
their
comments (two different templates) I was having AI Comment printout
in JSON format to my Action Item template and then parsing that on the
frontend.
So, <nowiki> should work perfectly fine in
template parameters.
>Unless you mean you want most wikitext to work, just not }} and friends.
In
which case there are two things you >could do: either have a separate
template containing just the characters (there is a built in template:!
>Where {{!}} Puts out a |). Or you can use entities e.g. { instead of
{
and } instead of } and | >instead of |.
--
bawolff
_______________________________________________
MediaWiki-l mailing list
To unsubscribe, go to:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-l