pillar icon indicating copy to clipboard operation
pillar copied to clipboard

Markup syntax and associated tools to write and generate documentation, books and slides

Results 120 pillar issues
Sort by recently updated
recently updated
newest added

I am having a serious problem with pillar that maybe you can help me understand: the attached file is not being parsed correctly. What I expect for this is to...

The testAnnotationAsPillar hardcodes the syntax for annotation and it would be better to use the builder. ``` testAnnotationAsPillar | res | res := self splitter pillarFrom: 'abc{!cite|a=2&b=5!}def'. self assert: res...

``` includedPillarAST := ((PRInputDocument inputClassForFile: includedFile) new "project: aProject;" file: includedFile contents; yourself) parsedDocument. ``` file: should expect a file reference and the parseDocument should do what it should. Then...

We should not forget to freeze microdown or we should not depend on the microdownDev baseline. ``` BaselineOfPillarApp ... "Microdown - we want it in App." spec baseline: 'MicrodownDev' with:...

``` caption ^ caption ifNil: [ caption := self parameters at: 'caption' ifPresent: [ :string | (PRDocument parser parse: string) children first ] ifAbsent: [ PRParagraph with: (PRText content: '')...

So that the PRParser is separated from the rest

acceptDecorated: aVisitor self accept: aVisitor is defined three to do exactly the same On Object and PRDocumentItem in addition it is invoked by ``` PRVisitor >> visit: anObject ^ anObject...

This is nice but why do we need to run all these tests for all the subclasses of PRObject especially when none of them refine such properties? I suggest that...

- should remove unused baseline - should remove unused config files