Skip to content

TeselaGen/tg-oss

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Teselagen's Open Source Mono Repo

Packages

@teselagen/ove (open-source vector editor - a tool for viewing and manipulating DNA/AA sequences)

@teselagen/ui (reusable react components)

@teselagen/bio-parsers (parsers and formatters for genbank/fasta/json/snapgene/geneious/jbei-xml)

@teselagen/sequence-utils (util functions for working with biological sequences (dna/rna/protein))

@teselagen/range-utils (util functions for working with biological ranges e.g. {start: 2, end: 61})

@teselagen/file-utils (util functions for working with files and blobs)

Contributing

This project welcomes contributions. Please have a look at the CONTRIBUTING file to learn about how to get started after a fresh clone.

License

All code from this repository is placed under the MIT License.

Publishing (works the same for all packages)

Simply bump the version in the package.json file and push to master. The GitHub Actions will handle the rest (updating dependencies, building, and pushing to gh-pages)

Note you will need to manually add an entry to the CHANGELOG.md file for the package you are publishing. New entries should be in the format:

0.1.0 (2025-01-05)

Publishing a beta version (for use when linking to a branch in another project)

Bump the version and add a "-beta" suffix to the version. Push to the beta branch. The GitHub Action will handle the rest.

Running tests

Unit tests are run automatically via precommit hook that runs a bun test command at the top level

Cypress e2e tests can be run locally via the following commands: nx run ove:launch-e2e nx run ui:launch-e2e

CI is run via GitHub Actions on every push and pull request and runs a suite of Cypress e2e tests

Adding a new package

Duplicate an existing package that is most similar to the new package being added and make the necessary changes.

You'll need to ask a Teselagen admin to update the trusted publishers settings in the npm registry for the new package (a maintainer will need to manually publish the first version in order to add it to the registry).

About

Teselagen Open Source modules

Resources

License

Contributing

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Contributors 19

Languages