Exporting some enums#89
Conversation
|
Hmmm... I would instead leave them in their respective module making them public and keep the same names. If someone wants to rename the import they can do it. Long names are never something I personally prefer. We can do breaking changes, it's not a big deal, especially bumping minor versions. And Thank you for the PR! |
|
Changed to make all modules under |
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #89 +/- ##
==========================================
- Coverage 80.35% 80.31% -0.04%
==========================================
Files 33 33
Lines 1196 1199 +3
==========================================
+ Hits 961 963 +2
- Misses 235 236 +1
☔ View full report in Codecov by Sentry. |
Changes
I Added below enums exporting.
RmcNavigationStatusGsaMode1GsaMode2PgrmzFixTypeI think it would be better to rename
NavigationStatustoGnsNavigationStatusto clarify the difference fromRmcNavigationStatus. However, this would be a destructive change, so I would like your opinion.I think it would be better to export the names of both
NavigationStatusandGnsNavigationStatus, but encourageNavigationStatusto use#[deprecated]to useGnsNavigationStatus.