Because rapido >=0.1.9 depends on path_provider ^0.5.0+1 and rapido <0.1.9 depends on path_provider ^0.4.1, every version of rapido requires path_provider ^0.4.1 or ^0.5.0+1.

Any chance of a new release please?

While writing the example below, I noticed that the onChanged function was not firing.

class _MyHomePageState extends State<MyHomePage> {
  DocumentList docs = DocumentList(
    "taskList",
    labels: {
      "Date": "date",
      "Task": "task",
      "Priority": "pri count",
      "Note": "note"
    },
    onLoadComplete: (DocumentList list) {
      list.sort((t1, t2) => t1["pri count"] - (t2["pri count"]));
    },
    onChanged: (DocumentList list) {
      print("taskList updated");
    },
  );

Hi,

When using the Parse persistance, the boolean field type is not supported because of the "?" at the end of the name of the field. With this label : "Available": "available?" in the documentList, Parse send this error ╭-- Parse Response Class: Products Function: ParseApiRQ.create Status Code: 105 Type: InvalidKeyName Error: Invalid field name: available?. ╰--

My Parse server is hosted on back4app.

I like this project and its very useful for apps where you have many of Master Detail forms to do CRUD on.

For the backend do you have thoughts yet ?

I have lately been using GraphQL flutter with graphQL backend in golang and getting good results in term of low friction for devs. https://github.com/zino-app/graphql-flutter

https://github.com/zino-app/graphql-flutter#roadmap

• has subscriptions, but i still need to get it working with golang backend using gqlgen

DocumentList.sort() works, but it could be simplified somewhat. For example:

documentList.setSortField("date", DocumentList.SortOrder.Ascending);

as well as something like:

 documentList.sortByTimestamp = true;

Could you do a "flutter create ." in the examples and add a reference to rapido in the pubspec. Makes its easier to work on this together and push examples back.

DocumentForm should only need to know about the Document it is creating or adding. It should not know about DocumentList.

1. Document will need an "onChanged" handler that DocumentList responds to.
2. Document will need to have a labels property, which can be supplied by the DocumentList or can be supplied directly.
3. The following code in DocumentForm will need to be modified to use labels on the Document, rather than the DocumentList, and to update the Document directly.

  List<Widget> _buildFormFields(BuildContext context) {
    List<Widget> fields = [];
    widget.documentList.labels.keys.forEach((String label) {
      dynamic initialValue;
      if (widget.index != null) {
        initialValue = widget.documentList[widget.index]
            [widget.documentList.labels[label]];
      }
      fields.add(
        Container(
          padding: EdgeInsets.all(10.0),
          child: TypedInputField(widget.documentList.labels[label],
              label: label,
              initialValue: initialValue, onSaved: (dynamic value) {
            newData[widget.documentList.labels[label]] = value;
          }),
          margin: EdgeInsets.all(10.0),
        ),
      );
    });

Widget CustomItem Builder(int index) {}

should be

Widget CustomItemBuilder(Document  document){}

in addition to #30 it would be:

Widget CustomItemBuilder(Document  document, BuildContext context){}

Currently, awaiting https://github.com/flutter/flutter/issues/25298 to be fixed. Meanwhile, maybe I can calculate the sort of correct zoom level using something like thisL https://stackoverflow.com/questions/6048975/google-maps-v3-how-to-calculate-the-zoom-level-for-a-given-bounds