Extensible wiki pages #505
Merged
Conversation
Attempting to move getHtml() and code to WikiPage.
Attempting to move getHtml() and code to WikiPage.
…kiPage. Needed the last change to make sure the page rendering does not distinguish between Wiki and Test pages
…nto WikiPageUtil.
The page factory expects the path to the page, not to the parent of a page. This allows for pages that use a name in FitNesse different from the one on fs.
Do not rely on parent pages for correct paths.
…temPage and SymbolicPage.
We're crossing subsystem borders here.
Conflicts: test/fitnesse/wiki/fs/FileSystemPageTest.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This pull request makes some serious changes to the way wiki pages work:
WikiPageFactory
s can be configured using theWikiPageFactories
configuration settingPageData
is no longer dependent on aWikiPage
WikiPage
is now responsible for rendering content,PageData
has become merely a containerWikiPage
s set their default properties themselves.WikitextPage
interface to facilitate in things like processing class pathsWikiPage
interfaceTestPage
is no longer a sub-interface ofWikiPage