Add a warning for unknown flake URI parameters #174

New issue

Closed

opened 2024-03-25 04:49:42 +00:00 by jade · 3 comments

jade commented

2024-03-25 04:49:42 +00:00

Owner

Currently you can put some garbage into a git+https://whatever?meow=2 url and then Lix will happily accept it without saying anything. This is bad UX.

Related: #87

Currently you can put some garbage into a `git+https://whatever?meow=2` url and then Lix will happily accept it without saying anything. This is bad UX. Related: https://git.lix.systems/lix-project/lix/issues/87

jade added the

E/help wanted

labels 2024-03-25 04:49:42 +00:00

jade added the

Area/flakes

label 2024-03-30 00:04:22 +00:00

ma27 self-assigned this 2024-04-26 21:26:43 +00:00

ma27 commented

2024-05-13 19:14:31 +00:00

Member

Just for documentation purposes since gerrit doesn't seem to do cross-linking, there's a pending CL in https://gerrit.lix.systems/c/lix/+/1102.

lix-bot commented

2024-06-03 09:55:14 +00:00

Member

This issue was mentioned on Gerrit on the following CLs:

commit message in cl/1102 ("libfetchers: make attribute / URL query handling consistent")

This issue was mentioned on Gerrit on the following CLs: * commit message in [cl/1102](https://gerrit.lix.systems/c/lix/+/1102) ("libfetchers: make attribute / URL query handling consistent")

ma27 commented

2024-06-23 16:34:27 +00:00

Member

Fixed by cl/1102.
Apparently I forgot to add a Closes ... in the commit message. Sorry!

Fixed by cl/1102. Apparently I forgot to add a `Closes ...` in the commit message. Sorry!

ma27 closed this issue

2024-06-23 16:34:27 +00:00

ma27 referenced this issue

2024-09-09 13:44:01 +00:00

Lix lockfiles differ Nix lockfiles #472