Replies: 1 comment
-
YES YES YES!!! I love when languages have a directory local environment (Rust, Julia, NodeJS), and I much prefer it to global environments that you have to do some inconvenient workarounds to wrap (Python's venvs). I think the manifest file should be called I think a basic initial schema with just metadata (as nothing will use it for now) could be something like this: name("name").
version(1,2,3). % Optional, enforce semver format or allow arbitrary version strings?
description("desc"). % Optional
authors(["author1", "author2"]). % Optional
license("MIT OR GPL-3.0-or-later"). % Optional, SPDX license expression
license_file("LICENSE"). % Optional, for custom licenses
repository("url"). % Optional
homepage("url"). % Optional Heavily inspired by Rust's |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'd like to solicit practices folks are using or maybe that we could consolidate around for the idea of a Scryer "project root".
In various languages there is some directory identified as a project root, even if it's a
.git
directory or aREADME.md
at minimum.I'm thinking of using a file called
project.pl
orscryer.json
as a project root. Of course there are tradeoffs about whether it's more ergonomic to use one or the other.Thoughts?
I like @hurufu's technique here but I'd like to recurse through subdirectories for "Scryer Projects" rather than have a single flat directory with them.
Beta Was this translation helpful? Give feedback.
All reactions