Skip to content

Commit

Permalink
go fmt with go 1.17
Browse files Browse the repository at this point in the history
The build tags have changed... I am highly sceptical of what this means for older go versions whose tests will likely now fail.

But as these are build tags, I cannot see how I can avoid updating them to the newer format.

This is the way for the future... if it breaks the past then hmmmm.
  • Loading branch information
buro9 committed Sep 2, 2021
1 parent cada0f0 commit 13d1799
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 0 deletions.
1 change: 1 addition & 0 deletions sanitize_go1.8_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@
// OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

//go:build go1.8
// +build go1.8

package bluemonday
Expand Down
1 change: 1 addition & 0 deletions sanitize_ltgo1.8_test.go
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,7 @@
// OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

//go:build go1.1 && !go1.8
// +build go1.1,!go1.8

package bluemonday
Expand Down
1 change: 1 addition & 0 deletions stringwriterwriter_go1.12.go
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
//go:build go1.12
// +build go1.12

package bluemonday
Expand Down
1 change: 1 addition & 0 deletions stringwriterwriter_ltgo1.12.go
Original file line number Diff line number Diff line change
@@ -1,3 +1,4 @@
//go:build go1.1 && !go1.12
// +build go1.1,!go1.12

package bluemonday
Expand Down

0 comments on commit 13d1799

Please sign in to comment.