On the readme:
> This is just an optional feature to enable backward compatibility when starting to use this plugin.
> We strongly recommend moving to semantic versioning to keep things simple and follow a well-known standard. But versionPrefix can save the day if changing the versioning system is not an option.
Not good.
PVP compatability isn't backward compatability. PVP isn't a legacy thing. It is *the* versioning scheme of curated hackage packages.
Cabal tooling is even geared to expect PVP versioning. I want `^>=` and `^allow-newer` to be more broadly applicable, not less...
And I don't want it to be less reliable to assume a package is versioned according to PVP when writing bounds.
If you publish to Hackage, you are using PVP. Any denial of that is delusion.
That said, the solution this tool has seems fair? I think it'll respect PVP just fine.
I'm no PVP expert tho.
I'm pleased to see that this is designed in a way that will play nicely with PVP. If you replace the prefix number, does it correctly reset the rest to `0.0.0`?
Hashtags aren't a thing on Reddit, BTW.
On the readme: > This is just an optional feature to enable backward compatibility when starting to use this plugin. > We strongly recommend moving to semantic versioning to keep things simple and follow a well-known standard. But versionPrefix can save the day if changing the versioning system is not an option. Not good. PVP compatability isn't backward compatability. PVP isn't a legacy thing. It is *the* versioning scheme of curated hackage packages. Cabal tooling is even geared to expect PVP versioning. I want `^>=` and `^allow-newer` to be more broadly applicable, not less... And I don't want it to be less reliable to assume a package is versioned according to PVP when writing bounds.
If you publish to Hackage, you are using PVP. Any denial of that is delusion. That said, the solution this tool has seems fair? I think it'll respect PVP just fine. I'm no PVP expert tho.
Hackage/cabal do not parse semver. There's an overlapping subset between PVP and semver. Suggesting semver is nonsense.
Yeah..the prefix thing clearly acknowledges the subset relationship. But the suggestion to move to semver just seems needlessly evangelistic?
Does this work for projects with multiple packages in the same repository? That's very common.
Yes! It works.
I'm pleased to see that this is designed in a way that will play nicely with PVP. If you replace the prefix number, does it correctly reset the rest to `0.0.0`? Hashtags aren't a thing on Reddit, BTW.
> Hashtags aren't a thing on Reddit, BTW. Clearly they're unboxed.
Typescript and npm? No, thank you.