Conversation
| }; | ||
|
|
||
| cargoLock = { | ||
| # Upstream does not include lock file |
There was a problem hiding this comment.
Can we ask upstream to include it?
There was a problem hiding this comment.
Upstream has now included a lock file, but it's not yet in the latest release.
Is it better to patch in a lock file, use the master git branch, or something else?
dotlambda
left a comment
There was a problem hiding this comment.
Commit message should be amber-lsp: init at 0.1.9.
cf792ca to
f02034a
Compare
This commit includes a Cargo.lock file for amber-lsp that I manually generated as upstream does not contain one.
f02034a to
3820c82
Compare
|
Would be great to move to latest (0.1.16) and include the cargoHash instead of vendoring the lock file. EDIT: will probably be blocked by this amber-lang/amber-lsp#106 |
Once this issue has been resolved I will update this PR. |
|
A fix has been implemented in v0.1.17, here's how I added a wapper to use the new env variable: |
I have added the Amber language server for the Amber programming language. I think this package will be useful, as the amber programming language has over 4.3k GitHub stars (at time of writing). Furthermore, the Amber programming language is already in nixpkgs (as amber-lang), so adding the language server will complement the Amber programming language package as an essential development tool.
This commit/PR includes a Cargo.lock file for the amber-lsp that I manually generated as upstream does not contain one. I will create a PR upstream and reference this PR and update this package derivation when upstream includes the lock file in the next release.
Things done
As part of building with "rustPlatform.buildRustPackage" the tests included in upstream for amber-lsp are executed, which all pass successfully.
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.