export providers and exact globe integration - #2
Merged
Conversation
Exports now resolve through an ExportProviderRegistry instead of a hardcoded switch, so integration packages can expose their own export formats next to the built-in ones. BudgetUsageService is no longer serialized with the queued export job.
The frontend export modal can now build its options dynamically instead of hardcoding the export types.
Restores the Exact CSV export removed in the previous codebase, now as an integration package. The ledger id mapping moved from a hardcoded config file to a per-budget-type Filament page stored in the integration config, and the export only appears once the mapping is configured.
The enum lists which period granularities an export offers rather than whether a date is required, and the periodOptions attribute in the export-formats endpoint now reflects that.
Exports without period options (like the current balance export) no longer demand a meaningless year parameter; their filename and mail drop the period as well.
tomasvanrijsse
force-pushed
the
feat/export-providers
branch
from
July 15, 2026 13:45
fee13cb to
38373ac
Compare
…stry The global-provider mechanism on ExportProviderRegistry only existed for the core exports; injecting the provider directly keeps the registry an exact mirror of TicketProviderRegistry.
Verbruik and Vrijval remain only in Filament labels and in the CSV content Exact expects; code and config keys use usage/release.
The table recordUrl fell back to IntegrationResource::getUrl('edit'),
but no edit page is registered, so listing an integration with an
unregistered type threw Route [filament.admin.resources.integrations.edit]
not defined. Return null instead so such rows are simply not clickable.
Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.