gofiber/template

🐛 [Bug]: django is broken after v3.1.0

Closed this issue · 2 comments

iredmail commented

Bug Description

django v3 is broken after v3.1.0.

$ go run main.go 
# github.com/gofiber/template/django/v3
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:21:7: undefined: core.Engine
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:31:16: undefined: core.Engine
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:46:16: undefined: core.Engine
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:64:16: undefined: core.Engine
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:81:4: e.Mutex undefined (type *Engine has no field or method Mutex)
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:82:10: e.Mutex undefined (type *Engine has no field or method Mutex)
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:86:15: e.Directory undefined (type *Engine has no field or method Directory)
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:89:7: e.FileSystem undefined (type *Engine has no field or method FileSystem)
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:92:55: e.FileSystem undefined (type *Engine has no field or method FileSystem)
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:94:55: e.FileSystem undefined (type *Engine has no field or method FileSystem)
../../.go/pkg/mod/github.com/gofiber/template/django/v3@v3.1.1/django.go:94:55: too many errors

How to Reproduce

Steps to reproduce the behavior:

  1. run sample code in README.md (https://github.com/gofiber/template/blob/master/django/README.md)

Expected Behavior

Works without error. Fiber listens on port 3000.

Template package Version

v3.1.1 and v3.1.2

Code Snippet (optional)

No response

Checklist:

  • I agree to follow Fiber's Code of Conduct.
  • I have checked for existing issues that describe my problem prior to opening this one.
  • I understand that improperly formatted bug reports may be closed without explanation.
ReneWerner87 commented

Sorry for that, we are working on a fix

iredmail commented

Confirmed #265 fixes the issue.