Repository navigation
Conversation
- Drop internal IMPLEMENTATION-SUMMARY.md worklog - Replace Beautech mentions in docs, docstrings, and tests with neutral wording - Anonymize a real production record and real-looking serials, tail numbers, and customer names in test fixtures and examples Co-authored-by: Igor <igor-ctrl@users.noreply.github.com>
engineOverviews, engineUtilizations, engineCards, and preservationStatuses were internal custom endpoint names. Swap them (and the private MCP tool names in docs) for generic equipment-* / inspectionStatuses examples. Co-authored-by: Igor <igor-ctrl@users.noreply.github.com>
test_make_bundle_produces_valid_manifest used make_bundle's default output path, dropping finance-2026.05.07-1.tar.gz into the repo root, where it was accidentally committed. Co-authored-by: Igor <igor-ctrl@users.noreply.github.com>
…nd tests Replace the remaining aviation-specific examples (engine utilization, ESNs, tail numbers, airworthiness tags, custom purchaseHeaders/Lines pages) with standard v2.0 entities such as customers, salesInvoices, purchaseInvoices and their lines, using CRONUS-style sample values. Custom-route tests use a neutral contoso/integration/v1.0 placeholder. Also drop the 'technical' SafeContext domain rule, which was identical to the default rule. Co-authored-by: Igor <igor-ctrl@users.noreply.github.com>
- registry import --from-file: JSON/YAML registry files or Postman collections; top-level publisher/group/version with bare entity names - registry import --from-metadata takes --publisher/--group/--version - imports merge instead of overwriting (--replace to start over; pack entries are kept) - registry export writes a portable file; pack presets accept it - entries with a partial custom route are rejected - short publisher/group/version keys accepted in registry entries - fix invalid '--from-metadata <metadata-url>' hint - rewrite docs/custom-apis.md and add examples/custom-apis.yaml Co-authored-by: Igor <igor-ctrl@users.noreply.github.com>
cursor
Bot
changed the title
This branch has not been deployed
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
2 participants
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.
Summary
Removes every organization-specific reference and all aviation-domain examples. The OSS now uses only Microsoft standard Business Central API v2.0 entities. This PR also makes registering your own AL API pages, and sharing them, a one-command step.
Changes
Company and domain scrub
IMPLEMENTATION-SUMMARY.mdworklog.engine*/purchaseHeaderspages. The replacements usecustomers,salesInvoices,purchaseInvoicesand their lines,generalLedgerEntries, and so on. Tests that need a custom route use a neutralcontoso/integration/v1.0/shipmentTrackingsplaceholder.technicalSafeContext domain rule. It was identical to the default rule, so behavior is unchanged.finance-*.tar.gzinto the repo root. That file had been committed by accident and is now removed.Custom APIs
bcli registry import --from-fileaccepts JSON or YAML registry files and Postman collections. A file can setpublisher/group/versiononce and list bare entity-set names. Seeexamples/custom-apis.yaml.--from-metadatanow accepts--publisher,--groupand--versiondirectly. Previously these had to be stored in the profile first.--replacerestores the old behavior but still keeps pack-owned entries.bcli registry exportwrites a portable file. Pack registry presets accept the same format./api/v2.0/.publisher/group/version.--from-metadata <metadata-url>.docs/custom-apis.mdand updated the README, getting-started, the command reference,AGENTS.md, andCHANGELOG.--from-postmanand--from-jsonstill work, but are now hidden in favor of--from-file.Test plan
uv run pytest tests/passes (1226 passed, 5 skipped)uv run ruff check src/ tests/is cleantests/test_registry/test_import_file.pyand two pack-loader testsregistry import --from-fileonexamples/custom-apis.yamland on the Postman fixture. The endpoints merged to 7, andendpoint infoshows the right route.registry exportround-trips.--from-metadatawithout a route exits 2 with a clear message.Breaking changes
bcli registry importnow merges by default. Anyone relying on it to replace the registry should pass--replace.Not addressed here: git history
Git history still contains the old content and a
@beautech.aeroauthor email on 19 commits. The plan is to start a fresh repo from this tree.