https://pact.io logo
Join Slack
Powered by
# pact-c-plus-plus
  • g

    GitHub

    04/20/2023, 10:05 AM
    #4 Feature Request: Implement API for generating contract using the v4 Pact Specification Issue created by adamdama Context We are currently undergoing a large scale project of adding contract testing to components being run on embedded devices. As embedded device components they are written in either C++ or Rust and compiled to binaries which are delivered out to the hardware devices. These components communicate between each other primarily in 5 ways: • Request + Response over HTTP • Synchronous Message interactions over WebSockets • Asynchronous Message interactions over WebSockets • Synchronous Message interactions over dbus • Asynchronous Message interactions over dbus For the HTTP Request + Response and asynchronous messages the current implementation of the C++ library using the v3 spec is sufficient. However a large amount of our inter-component communications are synchronous messages over WebSockets. We have not yet started looking at the dbus communications but that will come up in the not so distant future. We have written a pact plugin that supports WebSocket connections and have started using this to create contract tests between the components. This works really nicely in Rust as the Rust API is the reference and has support for synchronous message contracts and also loading plugins. However in C++ we have resorted to using the FFI functions directly. While this is working we feel that the developer experience is worse and there is a larger amount of effort involved when compared to using the fluid API interface of the pact-cplusplus library. The Request We would like to be able to use the pact-cpluscplus library to create Pact v4 spec contracts so that we can A) load plugins WebSockets and likely in the future dbus and B) create synchronous message contracts. Therefore we are requesting that the library be updated to offer this functionality. pact-foundation/pact-cplusplus
    👍 1
  • l

    Lewis Cowles

    12/20/2023, 10:36 AM
    @Lewis Cowles has left the channel
  • g

    GitHub

    06/26/2024, 12:15 PM
    #5 Message queues support for C++ Issue created by canny[bot] My company have a requirement to enable both ways communication with embedded device that runs C++ client, using the queues. I would like to ask if adding support for this is currently considered? Any chance this could be provided in short/medium perspective? https://pact.canny.io/admin/board/feature-requests/p/message-queues-support-for-c pact-foundation/pact-cplusplus
  • g

    GitHub

    12/01/2024, 11:41 AM
    #6 chore: Configure Renovate Pull request opened by renovate[bot] Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin. 🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged. --- Detected Package Files •
    .github/workflows/consumer.yaml
    (github-actions) •
    .github/workflows/release.yaml
    (github-actions) •
    .github/workflows/triage.yml
    (github-actions) •
    .github/workflows/trigger_pact_docs_update.yml
    (github-actions) Configuration Summary Based on the default config's presets, Renovate will: • Start dependency updates only once this onboarding PR is merged • Show all Merge Confidence badges for pull requests. • Enable Renovate Dependency Dashboard creation. • Use semantic commit type
    fix
    for dependencies and
    chore
    for all others if semantic commits are in use. • Ignore
    node_modules
    ,
    bower_components
    ,
    vendor
    and various test/tests (except for nuget) directories. • Group known monorepo packages together. • Use curated list of recommended non-monorepo package groupings. • Apply crowd-sourced package replacement rules. • Apply crowd-sourced workarounds for known problems with packages. 🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to
    renovate.json
    in this branch. Renovate will update the Pull Request description the next time it runs. --- What to Expect With your current configuration, Renovate will create 1 Pull Request: chore(deps): update actions/checkout action to v4 • Schedule: ["at any time"] • Branch name:
    renovate/actions-checkout-4.x
    • Merge into:
    master
    • Upgrade actions/checkout to
    v4
    --- ❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section. If you need any further assistance then you can also request help here. --- This PR was generated by Mend Renovate. View the repository job log. pact-foundation/pact-cplusplus GitHub Actions: build-osx GitHub Actions: build-ubuntu GitHub Actions: build-windows ✅ No checks have passed 0/3 successful checks