AppFlowy/frontend/appflowy_flutter
Alex Wallen e2009c063b
feat: Create a "view" for all database references in a document (#2083)
* feat: add archive for compression

* feat: add service to manage zipped work spaces

* feat: export service in barrel file

* feat: ignore .ephemeral directory

* feat: add first compressed workspace file

* fix: directory path was wrong

* feat: add a somewhat useful test

* fix: move to same file (delete later)

* fix: use script path vs. working directory for CI

* fix: read from asset bundle instead of file system

* fix: workaround to run integration in multiple files on desktop (flutter/flutter#101031

* feat: remove .ephemeral from .gitignore, no longer created

* feat: document test changes

* fix: lucas suggestion

* feat: mark assets as excluded in pubspec.yaml

* feat: add class for build utilities

* feat: add script runner for release builds

* feat: add build script as task in flowy project

* fix: typo in pubspec.yaml

* chore: use constants for exclude tag

* feat: add appversion as argument to build tool

* feat: use dart script in release.yml

* chore: remove task

* fix: careless error

Co-authored-by: Mihir <84044317+squidrye@users.noreply.github.com>

* feat: add translations for view of

* fix: typo in getAllDatabase

* feat: add view of database

* fix: remove unused import

* fix: use effective dart typing

* fix: insertPage marked as async, should return future

* fix: Remove multi-line string

* fix: ref can be null

* fix: unused imports caused analyzer to fail

* feat: also fix. Add empty document as option and change name to _name

* chore: move referenced database tests to empty document test file

* feat: add test utilities

* feat: add new integration test on an empty document

* feat: register test in runner

* fix: missing reference in insert_page_command

* fix: analyzer errors

---------

Co-authored-by: Mihir <84044317+squidrye@users.noreply.github.com>
2023-04-04 12:50:22 +08:00
..
android chore: sync release 0.1.1 (#2075) 2023-03-22 14:49:15 +08:00
assets feat: Create a "view" for all database references in a document (#2083) 2023-04-04 12:50:22 +08:00
integration_test feat: Create a "view" for all database references in a document (#2083) 2023-04-04 12:50:22 +08:00
ios chore: sync release 0.1.1 (#2075) 2023-03-22 14:49:15 +08:00
lib feat: Create a "view" for all database references in a document (#2083) 2023-04-04 12:50:22 +08:00
linux chore: sync release 0.1.1 (#2075) 2023-03-22 14:49:15 +08:00
macos chore: update to Flutter 3.7.5 (#2000) 2023-04-04 12:48:56 +08:00
packages chore: update to Flutter 3.7.5 (#2000) 2023-04-04 12:48:56 +08:00
test fix : Code block parser implementation (#2046) 2023-03-23 16:30:52 +08:00
web Feat/view map database (#1885) 2023-02-26 16:27:17 +08:00
windows chore: sync release 0.1.1 (#2075) 2023-03-22 14:49:15 +08:00
.gitignore feat: Create a "view" for all database references in a document (#2083) 2023-04-04 12:50:22 +08:00
.metadata chore: sync release 0.1.1 (#2075) 2023-03-22 14:49:15 +08:00
analysis_options.yaml Feat/view map database (#1885) 2023-02-26 16:27:17 +08:00
Makefile Feat/view map database (#1885) 2023-02-26 16:27:17 +08:00
pubspec.lock chore: update to Flutter 3.7.5 (#2000) 2023-04-04 12:48:56 +08:00
pubspec.yaml feat: Create a "view" for all database references in a document (#2083) 2023-04-04 12:50:22 +08:00
README.md chore: update to Flutter 3.7.5 (#2000) 2023-04-04 12:48:56 +08:00

AppFlowy_Flutter

Documentation for Contributors

This Repository contains the codebase for the frontend of the application, currently we use Flutter as our frontend framework.

Platforms Supported Using Flutter 💻

  • Linux
  • macOS
  • Windows

    We later expect to extend support to Android and iOS devices using Flutter.

Am I Eligible to Contribute?

Yes! You are eligible to contribute, check out the ways in which you can contribute to AppFlowy. Some of the ways in which you can contribute are:

  • Non-Coding Contributions
    • Documentation
    • Feature Requests and Feedbacks
    • Report Bugs
    • Improve Translations
  • Coding Contributions

To contribute to AppFlowy_Flutter codebase specifically (coding contribution) we suggest you to have basic knowledge of Flutter. In case you are new to Flutter, we may suggest you to learn the basics and then try to contribute, get started with Flutter here.

What OS Should I Use for Development?

We support all OS for Development i.e Linux, macOS and Windows. However, most of us promote macOS and Linux over Windows. We have detailed docs on How to Setup AppFlowy_Flutter in your local system in each OS.

Getting Started ❇

We have a detailed documentation, on how to get started with the project, and make your first contribution. However, we do have some specific picks for you.

Need Help?

  • New to GitHub? Follow these steps to get started
  • Stuck Somewhere? Join the Discord Group and we are there to help you!