Tree: d1f5bced4e

develop

docker/socat

drone-ci

master

v0.10

v0.10.1

v0.10.18

v0.10.8

v0.10rc

v0.11

v0.11.19

v0.11.29

v0.11.33

v0.11.34

v0.11.4

v0.11.43

v0.11.53

v0.11.66

v0.11rc

v0.2.0

v0.3.0

v0.3.1

v0.4.0

v0.4.1

v0.4.2

v0.5.0

v0.5.11

v0.5.13

v0.5.2

v0.5.5

v0.5.8

v0.5.9

v0.6.0

v0.6.1

v0.6.15

v0.6.3

v0.6.5

v0.6.9

v0.7.0

v0.7.19

v0.7.22

v0.7.33

v0.7.6

v0.8.0

v0.8.10

v0.8.25

v0.8.43

v0.9.0

v0.9.113

v0.9.128

v0.9.13

v0.9.141

v0.9.46

v0.9.48

v0.9.60

v0.9.71

v0.9.97

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from 'd1f5bced4e'

${ noResults }

Commit Graph

2 Commits (d1f5bced4e7eedcb6a34491c798982ec12c095ec)

Author	SHA1	Message	Date
Unknwon	63598688e4	pkg/markup: init default sanitizer.policy ... App would panic if user has validation error on installation and the sanitizer is not yet built. Therefore we need a minimal valid object for sanitizer at start.	8 years ago
Unknwon	d05395fe90	Refactoring: rename modules -> pkg ... Reasons to change: 1. Shorter than 'modules' 2. More generally used by other Go projects 3. Corresponds to the naming of '$GOPATH/pkg' directory	8 years ago
Unknwon	3a9276307c	modules/markup: move common functions to markup.go	8 years ago
Unknwon	761bb3cf53	modules/markup: protect sanitizer from possible modification ... Only expose public APIs for 'Sanitize' and 'SanitizeBytes' to eliminate unintentional modifications to sanitizer policy. Also use 'sync.Once' to make sure multiple calls of 'NewSanitizer' is safe (although should never happen, but this is a better way).	8 years ago