keller-mark/use-coordination

Renaming

Closed this issue · 1 comments

keller-mark commented
  • CmvProvider -> CoordinationProvider
  • @use-coordination/provider -> @use-coordination/core
  • useCoordinationScopesL1 -> useCoordinationScopes
  • useMultiCoordinationValues -> useCoordinationObject? Also, add to hooks page of docs
  • useCoordinationScopesL2 -> useCoordinationScopesL1
  • viewConfig -> spec in Zustand store
  • diffByKey -> remountOnKeyChange
  • config -> spec (everywhere)?
  • CmvConfig -> CoordinationSpec?
keller-mark commented

Vitessce to UseCoordination name changes:

  • useInitialCoordination -> _useInitialCoordination
  • useCoordination -> _useCoordination
  • useMultiCoordinationScopes -> _useCoordinationScopesL1All -> _useCoordinationScopesAll
  • useMultiCoordinationScopesNonNull -> _useCoordinationScopesL1 -> _useCoordinationScopes
  • useMultiCoordinationScopesSecondary -> _useCoordinationScopesL2All -> _useCoordinationScopesL1All
  • useMultiCoordinationScopesSecondaryNonNull -> _useCoordinationScopesL2 -> _useCoordinationScopesL1
  • useMultiCoordinationValues -> _useCoordinationObject
  • useComplexCoordination -> _useCoordinationL1
  • useComplexCoordinationSecondary -> _useCoordinationL2
  • useCoordinationScopes and useCoordinationScopesBy -> useViewMapping
  • VitessceConfig -> CmvConfig -> ?
  • viewConfig -> ?
  • useViewConfigStore -> useCoordinationStore
  • useViewConfigStoreApi -> useCoordinationStoreApi
  • ViewConfigProvider -> CoordinationStoreProvider
  • ViewConfigProviderLocal -> CoordinationStoreProviderLocal
  • createViewConfigStore -> createCoordinationStore
  • useSetViewConfig -> useSetSpec
  • remountOnUidChange -> remountOnKeyChange
  • store
    • state.initialViewConfig -> state.initialSpec
    • state.viewConfig -> state.spec
    • state.setViewConfig -> state.setSpec