You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's make the process even simpler by finding the source of ReasonML code (with an opt in to do it manually like we currently have).
setup would then look like:
$ add-reason setup
or
$ add-reason setup my-package-name
Recurse through project directory ignoring folders like /node_modules, /.**, and find all the directories that have *.re.
If we find multiple directories, fail and output a message
If we one multiple directory, save this as the "source" directory
Now continue like normal...
Other commands that need to know the source directory will also include this workflow.
Proposal of add-reason.lock
This lock file will be generated from every command unless a --no-lockfile flag is included. This file will store information that we glean from commands like:
The source directory path
The package name
This file will be used for all commands if it exists. This will allow a user to simply call something like
add-reason unlink
instead of
add-reason unlink my-package-name
Since we will have already known the package name. We could also keep other useful information here like is-linked: bool. I propose we only generate this file when a command has been executed successfully.
# THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
# add-reason lockfile v0.1.0
source: "/Users/nick/projects/add-reason/tests/root_for_testing/src/myCode"
name: "myCode"
is-linked: "true"
The text was updated successfully, but these errors were encountered:
New Workflow
Let's make the process even simpler by finding the source of ReasonML code (with an opt in to do it manually like we currently have).
setup
would then look like:or
/node_modules
,/.**
, and find all the directories that have*.re
.Other commands that need to know the source directory will also include this workflow.
Proposal of
add-reason.lock
This lock file will be generated from every command unless a
--no-lockfile
flag is included. This file will store information that we glean from commands like:This file will be used for all commands if it exists. This will allow a user to simply call something like
instead of
Since we will have already known the package name. We could also keep other useful information here like
is-linked: bool
. I propose we only generate this file when a command has been executed successfully.The text was updated successfully, but these errors were encountered: