But wouldn't you need a post per function to keep it somewhat organized and not one large post? And even then, they'll get buried based on how long since someone edited/posted to it. (Discourse doesn't really seem like the right tool for the job).
I had forgotten about this, but I started making a wiki for myself that I was gonna build up with a bunch of Ignition stuff on my homelab server that I never got around to actually adding much.
I can open it up (PM me if anyone wants a login to write posts).
I just made an Automation Professionals "book" if we want to test/play.
That was my idea. I suggested one thread per function (or maybe groups of similar / related functions) but Phil suggests that many examples will rely on multiple functions all at once and that it would be something like "task" based. I'm not sure how easy it would be to find what one was looking for.
Looks like it would be a good start. Really, once converted to Wiki style, if someone doesn't follow the style, it can be cleaned up by others, or tweaks to the style can be made afterward.
So, looking at your example, and a newbie trying to figure out what each function is actually doing, would it be helpful (I think it would be) to maybe give an explanation as to how it's functioning. For example:
Usage Explanation
forEach() - Iterates through each row of the dataset asMap() - Maps the values of the cells in each row as a key-value pair with the key being the column name. it() - Returns the index of each row so that the dataset is ordered properly??? (I really don't know on this one, which is why I'm asking if this would help, and I may be completely wrong on my previous assumptions as well)
Not bad. Probably would look nicer if the usage was in the same bullet list as the features employed. (Would be worth looking at the Iterables link I just added to better understand what forEach() is doing.
The forEach() makes a list of the mappings from calling asMap() on each row.
Should we add the line, // This expression uses Integration Toolkit functions.
as a header to each piece of sample code to encourage documenting the fact in projects? Someone maintaining a project wouldn't find any help in the IA documentation.
I wanted to do something like this for the CSS Useful Stuff topic I created, to avoid all the chatter surrounding the useful posts. Maybe I should convert that post to a wiki instead...
Eh, I don't immediately love it. I like the idea of keeping the body of knowledge on the forum but I'm not sure how well the wiki thread will scale; I guess if you let the search function to the heavy lifting it could be fine.
I'll keep my mess of Embr threads for now and let you prove out this idea
