You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm curious; currently the roadmap has "plugins" as a feature, but no mention of dev/prod parity with overrides similar to yarn workspaces with yarn pack*, or go mod** and replace directives (>1.11). I would presume that "plugins" as a feature is a "nice to have" rather than a core requirement, when developing software. How come the feature roadmap doesn't include proper version handling for local dependencies?
* yarn pack: will build all dependencies alike poetry build and keep their versions up to date in yarn.lock (rather than forcing a relative path in PKG-INFO
** go mod: works slightly worse than yarn pack because it updates the lockfile with this local dependency which requires you to mess with go mod before merging PR:s
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Poetry
-
I'm curious; currently the roadmap has "plugins" as a feature, but no mention of dev/prod parity with overrides similar to yarn workspaces with
yarn pack*, or go mod** and replace directives (>1.11). I would presume that "plugins" as a feature is a "nice to have" rather than a core requirement, when developing software. How come the feature roadmap doesn't include proper version handling for local dependencies?*
yarn pack: will build all dependencies alikepoetry buildand keep their versions up to date inyarn.lock(rather than forcing a relative path inPKG-INFO**
go mod: works slightly worse thanyarn packbecause it updates the lockfile with this local dependency which requires you to mess with go mod before merging PR:sBeta Was this translation helpful? Give feedback.
All reactions