lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [lucenenet] NightOwl888 commented on issue #229: Updates docs build
Date Tue, 20 Aug 2019 03:36:55 GMT
NightOwl888 commented on issue #229: Updates docs build
URL: https://github.com/apache/lucenenet/pull/229#issuecomment-522839428
 
 
   > Come to think of it, I already put in some special tokens so only the code sample
is grabbed and none of the surrounding junk that isn't important for the sample. They are
used by the CLI tool itself to display the code on screen.
   
   Scratch that, looks like the files don't have any tokens. The entire contents can be grabbed
and inserted except for maybe the license header (I think the CLI supports exclusion tokens,
but I ended up not using them). Is there some kind of placeholder we need in the doc files
so you can grab the latest code from the demo (looks like the demos could use some updates
to the cleaner APIs)? The demos map one-to-one to each one of the files in Lucene.Net.Demo.
Would those "blubs" happen to look exactly like the one in the benchmark docs, and if different,
could you go through and link them? Then I can go through the docs and pull out what is needed
and arrange the text around the code as appropriate.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message