Weaverbird is Toucan Toco's data pipelines toolkit, it contains :
- a pipeline Data Model, currently supporting more than 40 transformation steps
- a friendly User Interface for building those pipelines without writing any code, made with TypeScript, VueJS & VueX
- a set of BackEnds to use those pipelines :
- the MongoDB Translator that generate Mongo Queries, written in TypeScript
- the Pandas Executor that compute the result using Pandas dataframes, written in Python
- the Snowflake SQL translator, written in Python
For in depth user & technical documentation, have a look at weaverbird.toucantoco.dev
or at the documentation's source files in the docs
directory.
yarn install
See Dockerfile for supported node version
yarn build-bundle
This will generate an importable JS weaverbird
library in the dist
directory.
Important note: While we do our best to embrace semantic versioning, we do not guarantee full backward compatibility until version 1.0.0 is released.
The basic command to run all tests is:
yarn test
yarn format:fix
yarn lint --fix
yarn build-doc
This will run typedoc on the src/
directory and
generate the corresponding documentation in the dist/docs
directory.
The web documentation is powered by Jekyll.
All sources can be found in the docs
folder.
To build and run the documentation with docker:
cd docs/
docker buildx build -t weaverbird-jekyll .
docker container run --rm -p 4000:4000 -v $PWD:/jekyll weaverbird-jekyll
Once the docs are be built, they'll be available on http://localhost:4000
. Any change to a .md
source
file will trigger a rebuild.
put your
.md
file into thedocs
folder. You can add a folder as well to better organization
into your
.md
file don't forget to declare this at the beginning of the file :
---
title: your title doc name
permalink: /docs/your-page-doc-name/
---
to finish to get your page into the doc navigation you have to add it in `_data/docs.yml``
example :
- title: Technical documentation
docs:
- steps
- stepforms
- your-page-doc-name
Storybook uses the bundled lib, so all showcased components must be in the public API.
yarn storybook
This will run storybook, displaying the stories (use cases) of UI components.
Stories are defined in the stories/
directory.
This library is published on npm under the name weaverbird
automatically each time a release is created in GitHub.
-
Define new version using semantic versioning
-
Create a new local branch
release/X.Y.Z
from masterex:
release/0.20.0
-
Update the
version
property inpackage.json
and insonar-project.properties
-
Check differences between last release and current and fill
CHANGELOG.md
with updates-
Delete the
##changes
title at start of theCHANGELOG.md
if provided -
Add the date and version at start of
CHANGELOG.md
following this convention[X.Y.Z] - YYYY-MM-DD
ex:
[0.20.0] - 2020-08-03
-
-
Commit changes with version number
ex:
v0.20.0
-
Push branch
-
Create a pull request into master from your branch
-
When pull request is merged, create a release with the version number in tag version and title (no description needed)
ex:
v0.20.0
-
Hit the release "publish release" button (this will automatically create a tag and trigger the package publication )
-
Create a new local branch
chore/bump-server-version-x-x-x
-
Edit
server/pyproject.toml
& increment the version in[tool.poetry]
section -
Push branch
-
Create a pull request into master from your branch
-
Once the PR is approved & merged in master publish the release in Pypi with
make build
&make upload
<!-- Import styles -->
<link rel="stylesheet" href="weaverbird/dist/weaverbird.umd.min.js" />
<!-- Import scripts -->
<script src="vue.js"></script>
<script src="weaverbird/dist/weaverbird.umd.min.js"></script>
import { Pipeline } from "weaverbird";
By default, the CommonJS module is imported. If you prefer the ES module version, import
dist/weaverbird.esm.js
.
See the documentation generated in dist/docs
directory