The reason should be saved in some other place so the user can know what
is going on. The debug logs get cluttered with this and this would leak
the folder names.
These make reading the log files in bug reports really hard. Also it
contains some personal info, so I rather not have them.
I can look into another way of showing the user why certain files were
ignored.
This changes the way the SSH keys are managed, they are no longer
managed by the git_bindings plugin and are instead just passed as
parameters. They are now saved in shared_prefs. This allows us to easily
have multiple ssh keys.
It also allows us to store the ssh keys in a more secure storage
location in the future.
Earlier we had one folder 'journal_local', when the remote would be
setup a new folder called 'journal' would be created, and each all the
files would be copied over. This meant the local history was being
destroyed.
Now, we only have 1 folder 'journal', and on 'cloning', we add the url
as a remote, and do a git fetch + merge.
This simplifies everything drastically, and opens the door for multiple
remotes.
Stop it being a singleton. This means it needs to be passed around a
lot. This sucks, but it's how it should be. I shouldn't be using a
global variable to get around this.
This is needed as Settings will soon become repo specific when we
support multiple repos.
This breaks saving the settings in a file, that feature was toggled off
anyway. It needs to be thought over again.
This way we can swap the merge out easily for our own custom merge code.
Also, this makes it easier to do a merge as a way of migrating.
This commit probably breaks stuff on ios
Nodes which have a pos < 0, are no longer force directed. This make the
graph behave strangely. It's better to just push it a little further
from the edge.
The one in the current stable branch is buggy and the scaling doesn't
work reliably.
This is from the beta branch.
This breaks selecting a node and being able to move it easily.
I'm testing this with the Foam documentation. This has revealed a number
of bugs in our link resolver - most of which have now been fixed.
The graph layouting is not being done as this is so incredibly slow.
This has been added as an experimental feature.
We were mixing up header links with wiki links and the alt text. It was
a bit messy. We currently do not support linking to a particular part of
a note. Nor do we support wiki links as link references.
Fixes APP-A0
Our MdYamlCodec runs inside an isolate, and send the result back. The
YamlMap data structure doesn't seem to be serializable over an isolate
and gives us an error. Therefore, we should make sure it is a normal
map.
A user requested that the YAML header be present at the bottom. I
thought this would be quite simple, but there are lots of edge cases
which will need to be solved.
Related to #223
