We have a code of conduct, please make sure to review it prior to contributing.
- Branch off
- One feature per commit.
- In case of changes request, amend your commit.
- There is a
hooks/pre-commitfile which can be used as a
pre-commitgit hook to check coding style.
- Python coding style is PEP8. JS coding style is enforced by
- Some useful
npmscripts are provided (
Translating the webapp
If you want to translate the webapp, just create a new folder in
flatisfy/web/js_src/i18n with the short name of your locale (typically,
is for english). Copy the
flatisfy/web/js_src/i18n/en/index.js file to this
new folder and translate the
flatisfy/web/js_src/i18n/index.js file to include your new
How to contribute
- If you're thinking about a new feature, see if there's already an issue open about it, or please open one otherwise. This will ensure that everybody is on track for the feature and willing to see it in Flatisfy.
- One commit per feature.
- Branch off the
- Check the linting of your code before doing a PR.
- Ideally, your merge-request should be mergeable without any merge commit, that
is, it should be a fast-forward merge. For this to happen, your code needs to
be always rebased onto
master. Again, this is something nice to have that I expect from recurring contributors, but not a big deal if you don't do it otherwise.
- I'll look at it and might ask for a few changes. In this case, please create new commits. When the final result looks good, I may ask you to squash the WIP commits into a single one, to maintain the invariant of "one feature, one commit".
Adding support for a new Weboob backend
To enable a new Weboob
CapHousing backend in Flatisfy, you should add it to
the list of available backends in
and update the list of
BACKEND_PRECEDENCES for deduplication in
Adding new data files
If you want to add new data files, especially for public transportation stops (to cover more cities), please follow these steps:
- Download and put the original file in
flatisfy/data_files. Please, use the original data file to ease tracking licenses and be able to still have a working pipeline, by letting the user download it and place it in the right place, in case of license conflict.
- Mention the added data file and its license in
README.md, in the dedicated section.
- Write a preprocessing function in
flatisfy/data_files/__init__.py. You can have a look at the existing functions for a model.
Adding new migrations
If you want to change the database schema, you should create a matching migration. Here is the way to do it correctly:
- First, edit the
flatisfy/modelsfiles to create / remove the required fields. If you create a new database from scratch, these are the files which will be used.
- Then, run
alembic revision -m "Some description"in the root of the git repo to create a new migration.
- Finally, edit the newly created migration file under the
migrations/folder to add the required code to alter the database (both upgrade and downgrade).