- 01 Nov, 2016 1 commit
-
-
panjan authored
Fixes: https://gitlab.com/gitlab-org/gitlab-ce/issues/18096
-
- 16 Oct, 2016 1 commit
-
-
Ebrahim Byagowi authored
-
- 14 Sep, 2016 1 commit
-
-
Qingping Hou authored
-
- 01 Jul, 2016 1 commit
-
-
Grzegorz Bizon authored
-
- 10 Jun, 2016 1 commit
-
-
Paco Guzman authored
-
- 09 Jun, 2016 1 commit
-
-
Timothy Andrew authored
Original Comments ================= - Linking behaves as per rules documented here: https://gitlab.com/gitlab-org/gitlab-ce/blob/16568-document-wiki-linking-behavior/doc/markdown/wiki.md - All links (to other wiki pages) are rewritten to be at the level of the app root. We can't use links relative to the current page ('./foo', 'foo', '../foo'), because they won't work in the markdown preview, where the current page is suffixed with `/edit` - Move existing `WikiLinkFilter` specs to `WikiPipeline` spec. It makes sense to run these tests on the combined output of the pipeline, rather than a single filter, since we can catch issues with conflicting filters. - Add more tests to cover the new linking @rymai's Review =============== - Classes nested under `WikiLinkFilter` should declare `WikiLinkFilter`'s inherit, so nothing changes if the nested class is loaded first. - Add a blank line after a guard clause - Use keyword arguments for the `Rewriter` constructor - Invert a condition - use `if` instead of `unless` - Inline a `let` in `WikiPipeline` spec - it was only used in a single place - Change out of date spec names - Add a comment for every rewrite rule in `Rewriter`
-
- 06 Apr, 2016 2 commits
-
-
Gabriel Mazetto authored
-
Gabriel Mazetto authored
-
- 17 Mar, 2016 3 commits
-
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
Grzegorz Bizon authored
-
- 03 Mar, 2016 1 commit
-
-
Robert Speicher authored
-
- 01 Mar, 2016 1 commit
-
-
Robert Speicher authored
Removes the specs from GollumTagsFilter that were more like integration tests for the pipeline than unit tests of the filter.
-
- 03 Feb, 2016 1 commit
-
-
Robert Speicher authored
This allows for future pipelines to more easily define a custom whitelist.
-