cbba9ade49
chore: Update the analytics backend url
2024-08-25 13:23:39 +02:00
657721adc6
Update dart-git and stop using the Result class
...
Instead we're going to move back to standard exceptions.
Using a custom Result class has created far far more problems
- The Stacktraces aren't always right
- Sometimes one forgets to check the Result error
- All other exception throwing code needing to be converted to Results
- Non idiomatic Dart code
I think it's better to just go back to exceptions. They have their
problems, but overall, I think it's a better approach.
2023-11-24 14:03:30 +01:00
ca98da4029
Update deps and fix linting issues
2023-01-20 16:14:08 +01:00
a322879077
make fmt
2022-06-26 15:15:11 +02:00
feade7fd70
Fix lint
2022-06-26 15:10:20 +02:00
f6eac10717
Send the Analytics data as an http post
...
Using DIO for sending binary data is very very difficult. It has taken
me over 45 minutes to figure out that Dio changes the body in some
strange ass manner unless I sent it as a stream.
WTF is this strange library.
Related -
* https://github.com/flutterchina/dio/issues/307
* https://github.com/flutterchina/dio/issues/837
2022-06-25 16:06:34 +02:00
557a02e01a
Analytics: Use a simple post instead of grpc
...
Much easier on the backend side. GRPC is way way more complex than I
expected.
2022-06-25 16:06:34 +02:00
901e4b5cb9
Avoid importing dart_git's Result class
...
It's easier to see where all dart_git is used this way, and this result
class should be refactored into its own package anyway.
2022-01-22 10:11:45 +01:00
28f34ca5e6
Avoid catching only Exceptions
...
We also occasionally get Errors in runtime. It seems like a terrible
decission for Error and Exception to not have a common subtype.
2021-10-20 09:59:14 +02:00
33a731a3d7
Add reuse licensing to files in lib
2021-09-15 13:06:43 +02:00
3fb07afd6e
Analytics: Increase timeout for sending the data
2021-09-07 14:29:37 +02:00
8245c35e73
Change analytics endpoint
2021-08-26 15:25:12 +02:00
7ff61d2f41
Disable dart-code-metrics for now
...
Even though I'm not using v4.2, the return-value rule is still being
applied with `flutter analyze` though not consistently.
For now, lets disable this, as there are 300+ warnings to fix.
2021-08-25 11:17:21 +02:00
d63b77d591
Analytics: Fix network
2021-08-16 13:44:14 +02:00
103197b886
Analytics: Send to backend when possible
2021-08-12 00:10:18 +02:00
f14e754b74
anaytics example: Use the right port
...
This took me way way too long to figure out
2021-08-09 18:18:03 +02:00
0e2adf8bb6
Analytics: Add sample network code
...
This doesn't seem to work. I'm not sure what I've done wrong with
google cloud run.
2021-08-09 17:23:18 +02:00
