makes some field optional in the nickel #30

New Issue

GuilloteauQ · 2024-08-01T17:47:30+02:00

GuilloteauQ commented

2024-08-01 17:47:30 +02:00

https://nickel-lang.org/user-manual/syntax#metadata

antux18 commented

2024-08-02 09:22:49 +02:00

I suppose we could set the "doi" and "comment" sections to optional. Are you thinking of another section?

GuilloteauQ commented

2024-08-02 10:12:19 +02:00

doi must stay mandatory.

What i have in mind:

Mandatory:
artifact_url
type
doi

Optional with a default value:
version (default = "1.0")
comment (default = "")
git_packages (default = [])
misc_packages (default = [ ])
python_venvs (default = [])

Unclear if it should be mandatory or optional with a default value:
package_managers

doi must stay mandatory. What i have in mind: Mandatory: artifact_url type doi Optional with a default value: version (default = "1.0") comment (default = "") git_packages (default = []) misc_packages (default = [ ]) python_venvs (default = []) Unclear if it should be mandatory or optional with a default value: package_managers

antux18 commented

2024-08-02 10:40:56 +02:00

Okay, I see better now, we could set a default value.

Package managers could be optional, with a default value of [], imo, because there could be evil Dockerfiles that only use Git/Misc packages and no package manager.

Okay, I see better now, we could set a default value. Package managers could be optional, with a default value of [], imo, because there could be evil Dockerfiles that only use Git/Misc packages and no package manager.

antux18 added the

Kind/Enhancement

Priority

Low

labels 2024-08-05 16:02:41 +02:00

antux18 referenced this issue from a commit

2024-08-06 11:45:29 +02:00

Now optional with a default value in the Nickel contract: version, comment, git_packages, misc_packages, python_venvs (close #30).

antux18 closed this issue

2024-08-06 11:45:29 +02:00

Sign in to join this conversation.