Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clean up the inputs directory #310

Open
EvanKirshenbaum opened this issue Jan 30, 2024 · 0 comments
Open

Clean up the inputs directory #310

EvanKirshenbaum opened this issue Jan 30, 2024 · 0 comments
Labels
3 medium Issue of medium importance is: housekeeping Issue relates to code organization

Comments

@EvanKirshenbaum
Copy link

The inputs folder contains a lot of files, many of which are out of date, but some of which are being used by various projects, so I don't want to get rid of them just yet. I've gotten rid of the ones I'm sure were just mine (e.g., for compiler and Opentrons testing), but the rest probably should be pruned (or moved to an org-specific folder) as soon as we can warn people to do so.

The only ones that should probably stay are

  • example.dml
  • .logging
  • .ot2.json
  • .reagents.json

I'm currently adding a README.md file that warns people that the other .dml (and, worse, .dmf) files shouldn't be trusted as examples of DML syntax.

Migrated from internal repository. Originally created by @EvanKirshenbaum on Jan 28, 2024 at 2:28 PM PST.
@EvanKirshenbaum EvanKirshenbaum added 3 medium Issue of medium importance is: housekeeping Issue relates to code organization labels Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 medium Issue of medium importance is: housekeeping Issue relates to code organization
Projects
None yet
Development

No branches or pull requests

1 participant