Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: eclipse-emfcloud/modelhub
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: eclipse-emfcloud/modelhub
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: update-to-241014
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 20 files changed
  • 1 contributor

Commits on Oct 28, 2024

  1. Add latest features 

    Contributed on behalf of STMicroelectronics

Co-authored-by: Christian W. Damus <cdamus.ext@eclipsesource.com>
Co-authored-by: Anthony Fusco <anthony.fusco@st.com>
Co-authored-by: Camille Letavernier <cletavernier@eclipsesource.com>
Co-authored-by: Stefan Dirix <sdirix@eclipsesource.com>
Co-authored-by: Maxime DORTEL (STM) <maxime.dortel@st.com>
Co-authored-by: Nina Doschek <ndoschek@eclipsesource.com>
Co-authored-by: Gabriel GASNOT <gabriel.gasnot@st.com>
Co-authored-by: FlorentPastorSTM <florent.pastor@st.com>

* feat: Deferred compound commands API
Implement a new API for construction of late-defined compound
commands, in which
- the scope of model edits is declared up-front to exclude concurrent
  commands that would interfere
- executability of the compound does not require the commands to be
  known a priori
- a separate can-execute predicate can be provided that asserts the
  executability of the commands without actually having to prepare them
- a strict option does allow to prepare the compound for executability
  test delegating to its contained commands
- document the primary use case for the deferred compound command

* fix: clear frontend subscriptions on modelhub dispose
Previously, when a ModelHub was disposed in the backend, the cached
frontend pipelines were not cleared. Therefore a subscription to a now
no longer existing ModelHub was reused when a ModelHub with the same
context was created. As a consequence new frontend subscription to the
following ModelHubs were not notified. This is now fixed.
    @eneufeld
    eneufeld committed Oct 28, 2024
    Configuration menu
    Copy the full SHA
    40d566e View commit details
    Browse the repository at this point in the history
Loading