pub.dev

baato_api

Flutter package to consume Baato APIs. You can search for places, reverse geo code and request for directions for several modes of transportation, including bike, foot and car.

baato/baato-flutterNew releases in your daily digest, changelog included.

Latest stable

2.2.0

Last release 3 months ago
28 Jul 2026
Release timing varies
gaps range from 2 weeks to 1.9 years
Nearly every release is documented
notes for 12 of 13 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
13 releases · first in 2020

Releases on this page

Drag across the ruler to compare, or tap a release to open it.

2.2.028 Jul 2026Deprecated
Replaced bare @deprecated annotations with @Deprecated('...') messages across the legacy API surface.
Added a root analysis_options.yaml applying package:flutter_lints, which was declared as a dev dependency but never actually enabled.

Resolved all 174 static analysis issues; dart analyze is now clean.

Removed leftover debug statements in BaatoDirectionAPI that printed the full decoded response body on every directions request. These wrote response payloads to stdout in release builds.

Library logging now uses debugPrint instead of print, so output is suppressed in release builds. This covers both the opt-in LogInterceptor and the internal error handler, which previously printed unconditionally.

Replaced bare @deprecated annotations with @Deprecated('...') messages across the legacy API surface.

Applied dart format to lib/.

WASM compatibility

The package is now WASM-compatible. package_info_plus is reached through a conditional import (app_id_native.dart / app_id_web.dart) instead of being imported directly.

This was necessary because package_info_plus unconditionally exports a dart:io based Linux implementation from its entry point:

export 'src/package_info_plus_linux.dart'; // no condition export 'src/package_info_plus_windows.dart' if (dart.library.js_interop) 'src/package_info_plus_web.dart';

That first export pulls dart:io into every target, including WASM. The problem is present in 10.2.1 as well, so upgrading does not avoid it.

Behaviour change on web: the automatic appId fallback is not available on web or WASM, because package_info_plus cannot be imported there at all. Web callers should pass appId explicitly to BaatoAPI.configure(). All other platforms are unaffected and keep the automatic fallback.

No public API changes.

Your coding agent can read these notes before it upgrades. Set up the MCP server →

Release timeline

13 releases since 2020

2.1.028 Jul 2026Breaking

No breaking changes. The public Dart API and the minimum Dart SDK (>=3.6.0) are unchanged, so upgrading from 2.0.1 requires no source or toolchain cha…

Upgraded dependencies:
- dio: ^5.9.0 → ^5.11.0
- crypto: ^3.0.6 → ^3.0.7
- package_info_plus: ^8.3.0 → ^8.3.1
- flutter_lints: ^5.0.0 → ^6.0.0 (dev)
Declared the previously implicit flutter: ">=3.19.0" constraint.
No breaking changes. The public Dart API and the minimum Dart SDK (>=3.6.0) are unchanged, so upgrading from 2.0.1 requires no source or toolchain changes.

package_info_plus is intentionally held at 8.3.x. The 9.0.0 and 10.0.0 releases are breaking and would push Dart >=3.10.0, Flutter >=3.38.1, Android AGP >=8.12.1 / Gradle >=8.13 / Kotlin 2.2.0, iOS >=13.0 and macOS >=10.15 onto every consumer. This package uses exactly one symbol from it (PackageInfo.fromPlatform().packageName, as a fallback when no appId is supplied), which does not justify that cost.