Regarding package renaming from github.com/antonmedv/expr to github.com/expr-lang/expr #492
Replies: 2 comments 2 replies
-
Yes, as I'm planning on adding more related project to expr under expr-lang org (js parser, editor, etc). See #481
I'm not sure how I can do it without publishing antonmedv/expr again. Rignt now https://github.com/antonmedv/expr redirects to https://github.com/expr-lang/expr
I think it will break old code what uses older version of Expr.
Please, explain. Only I can publish under antonmedv/expr.
Me nether 🙃. I added a section in readme about the move. |
Beta Was this translation helpful? Give feedback.
-
Thanks, @antonmedv . If we keep https://pkg.go.dev/github.com/antonmedv/expr active, then we need to make sure that it is at par with https://pkg.go.dev/github.com/expr-lang/expr. If the former lags behind then people who don't move to the newer package will unkowningly keep on using old code. If we could make https://pkg.go.dev/github.com/antonmedv/expr use the git repo https://github.com/expr-lang/expr, then I believe we will get the best of both worlds (i.e nothing will break for users who don't import the new package, and yet they will get the latest updates from the expr-lang repo). |
Beta Was this translation helpful? Give feedback.
-
Starting a discussion regarding renaming. The intention is to (at the very least) bring out ideas from everyone.
@antonmedv I currently see two copies of expr in the go package library: old package name, as well as new package name . This is the reason
Beta Was this translation helpful? Give feedback.
All reactions