e Rijk
>>>
>>>
>>>
>>> Sent from my iPhone
>>>
>>> > On 9 May 2017, at 02:23, Otto Fowler >> > <mailto:ottobackwa...@gmail.com>> wrote:
>>> >
>>> > There is a readme.md <http://re
er in 777.
> I only stubbed them out however.
>
> Each parser created by the archetype has one as well.
>
> What I was hoping to do was to include the parser docs in the package
assembly so the UI could load it.
>
>
>
> On May 8, 2017 at 19:35:41, Simon Elliston Ball
iPhone
> On 9 May 2017, at 02:23, Otto Fowler wrote:
>
> There is a readme.md PER parser in 777.
> I only stubbed them out however.
>
> Each parser created by the archetype has one as well.
>
> What I was hoping to do was to include the parser docs in the package
assembly
gt;
>> On 9 May 2017, at 02:23, Otto Fowler wrote:
>>
>> There is a readme.md PER parser in 777.
>> I only stubbed them out however.
>>
>> Each parser created by the archetype has one as well.
>>
>> What I was hoping to do was to include the parser docs in
Rijk
Sent from my iPhone
> On 9 May 2017, at 02:23, Otto Fowler wrote:
>
> There is a readme.md PER parser in 777.
> I only stubbed them out however.
>
> Each parser created by the archetype has one as well.
>
> What I was hoping to do was to include the pa
.
What I was hoping to do was to include the parser docs in the package assembly
so the UI could load it.
On May 8, 2017 at 19:35:41, Simon Elliston Ball (si...@simonellistonball.com)
wrote:
Quick thought, and please shoot me down if this has already been thought of,
but….
Would it be
There is a readme.md PER parser in 777.
I only stubbed them out however.
Each parser created by the archetype has one as well.
What I was hoping to do was to include the parser docs in the package assembly
so the UI could load it.
On May 8, 2017 at 19:35:41, Simon Elliston Ball (si
Casey Stella wrote:
> +1 for parser docs
>
> On Mon, May 8, 2017 at 7:35 PM, Simon Elliston Ball <
> si...@simonellistonball.com> wrote:
>
> > Quick thought, and please shoot me down if this has already been thought
> > of, but….
> >
> > Would it be wort
+1 for parser docs
On Mon, May 8, 2017 at 7:35 PM, Simon Elliston Ball <
si...@simonellistonball.com> wrote:
> Quick thought, and please shoot me down if this has already been thought
> of, but….
>
> Would it be worthwhile if we put some per parser docs into the repo,
> es
Quick thought, and please shoot me down if this has already been thought of,
but….
Would it be worthwhile if we put some per parser docs into the repo,
essentially a README.md per major parser class, which would in theory be picked
up by the docbook? We don’t really have much documentation
10 matches
Mail list logo