We now have a list of all the features that are implemented, and we can
use that to show a kind of feature list which can be used to -
1. Move away from app rental model
2. Showcase a feature list; see WorkingCopy
Make it a ChageNotifier and try to access it through the Provider
instead of like a global variable. This way, the state is better
managed and it'll be easier to split out Settings into smaller classes.
This basically asserts if we move to a route without a name. This way
I'll always catch when a route doesn't have a name, and I can start
getting better analytics on which screens are used most frequently.
This will show all the debug messages, which include when a file is
being ignored and not loaded, and hopefully all the exceptions. So the
user should be able to better understand why a file has been ignored.
It's not an ideal solution, but it's a quick fix.
Fixes#122
Ever since we had a proper markdown renderer, this option has been
broken as it only scales the body text and not the headers, and other
text in code-blocks. Additionally it only modifies the viewing text size
and not the editing text size. Fixing this feature is way too much work,
and barely any users are using this feature.
Maybe we will introduce it again in the future.
Some people are using GitJournal to edit Hugo websites, this option is
for them as the Hugo front matter uses the 'lastmod' key to indicate
when the post was last modified.
This way you can regenerate the SSH Key (if needed) and/or copy it
again. In the future one can add methods to reconfigure the git remote
and add / remove remotes.
It's better to have our own small class for this as the one provided
with the library tries to contact the PreferencesService and that isn't
what we want.
* Use a DialogBox instead of a drop-down - This conforms better to the
Material design spec.
* Make the enum into a class. It makes managing it much easier. And
avoids code duplication.
