Fixes#972
This required regenerating the protobufs generated files, which seem to
have tons of extra changes, and needed some manual changes to get them
to compile.
Overall, the entire protobuf idea wasn't the best in retrospect, and in
the next version of GitJournal, I'll be going with a simple relational
database instead.
This reverts commit 48ca5b8941368c99d153824734e59c6930251aae.
We've had to downgrade Flutter and the latest has a regression with
zlib, and the newer gradle conversion doesn't seem to be working. I
rather just revert and revert the revert another day.
Build file '/Users/vishesh/src/journal/android/app/build.gradle' line: 36
* What went wrong:
A problem occurred evaluating project ':app'.
> Could not get unknown property 'versionCode' for extension 'flutter' of type FlutterExtension.
Flutter 3.24 still has the regression of the ZlibDecoder and therefore
cannot be used. 3.24.1 also still has it. Hopefully this will be fixed
in 3.24.2
This is supposed to create a zip of all the files in the repo, and its
.git folder. It's super useful for debugging the state of the repo, and
it's also useful when the remote is down but you still have changes
which you want to export.
Both this calendar view and this history screen need a lot of work to
get them to a place where they can be shipped, and there are no plans of
doing that.
Without it - only on Android - we get the following error -
The following NoSuchMethodError was thrown building LayoutBuilder:
I/flutter ( 4269): Class '_LayoutBuilderElement<BoxConstraints>' has no instance method 'watch'.
I/flutter ( 4269): Receiver: Instance of '_LayoutBuilderElement<BoxConstraints>'
I/flutter ( 4269): Tried calling: watch<MarkdownRendererConfig>()
This makes no sense to me, but it fixes it. So so strange.
Cause this code works when running the app on macos.
We have a newer version of Flutter out, but I prefer to wait a few
months before all the relevant packages upgrade, as I'm already getting
tons of errors.
The only use of it left was to generate RSA keys, this has now been
implemented in the dart-go-git library, even though that's probably not
the right place for it.
As much as I like the idea of this, this is the second time the CI is
failing and I can't understand why. My local version of Flutter is
identical.
And running the CI again then made it pass. It seems that this has some
false negatives.
This commit was already in PR #625 but this new one is based on a more
recent version of the master branch.
As discussed in https://github.com/GitJournal/GitJournal/pull/625 the
problem was that if there is no yaml header, the title does not get
stored anywhere and hence gets lost. The fix is to write the title back
to the file as a first heading. This is used for loading the title
anyway, afaict.
The side effect is of course that any *other* application using the note
in the meantime will see the heading containing the note title. This is
way less disruptive than losing the title fully, though.
Lets use dart-git instead. It seems stable enough, and I'm soon going to
be moving away from libgit2 to go-git anyway. This is the first step towards
that.
Maybe this will fix the CI issue. Not sure why it says that pubspec.yaml
and lock file aren't synced, when at least locally they very much seem
to be.
I doubt this will fix the issue. But lets see.
