Alexandru Popovici
e80e0de74c
* feat(viewer-lib): Added MeasurementData and stuck with shared library defined measurement related types * feat(viewer-lib): Some updates: - Removed unnecessary calculations in point to point measurement. More lean now. Implemented serialization/deserialization - Tempoarary serialization/deserializaton for the rest of the measurement types - MeasurementsExtension now is able to load measurements from MeasurementData objects - Updated viewer's export list to not export mesurements related types that are now exclusively exported by the shared library * feat(viewer): Perpendicular measurements simplification (a little bit) and serialization/deserialization * chore(frontend): Updated measurement types imports * chore(viewer-lib): Removed the old normal indicator line from the perpendicular measurement * feat(viewer-lib): Updates: - Generic fromMeasurementData and toMeasurementData for all measurements since it's unniversal - Each measurement type serializes/deserializes only specialized data - Implemented ponint measurement serializing/deserializing and programmatic functionining * feat(viewer-lib): Area mesurement serialization/deserialization * feat(viewer-lib): Updates: - Each measurement subtype now reports the MeasurementType it belongs to - MeasurementsExtension now emits a MeasurementsChanged event with all the measurements as payload whenever the measurements change - units and precision are no longer serialized/deserialized on a per-measurement basis - Added sync API member addMeasurement * chore(viewer-lib): Fix compiler error * chore(viewer-lib): Added measurements getter in MeasurementExtension * feat(fe2): save/reload measurements integration (#5351) * measurements idempotent api * extra adjustments, stuff seems to work * lint fix * more lint fix * fix for visible going false * better identification * fix FlyControls change action --------- Co-authored-by: Kristaps Fabians Geikins <fabians@speckle.systems>
@speckle/shared
This package holds code that otherwise would be duplicated across @speckle packages, things like helpers, constants and TS types.
Usage
Peer dependencies
Some dependencies are marked as peer dependencies, to ensure that package consumers can manage their versions themselves. If you use any code from this package that relies on a specific peer dependency, make sure its installed.
How to use
import { Roles, RichTextEditor } from '@speckle/shared'
There are also "heavy" imports, that are not exported by default, like @speckle/shared/environment. These are used to avoid importing the whole package when only a small part of it is needed.
If export maps don't work (due to a legacy TS configuration) you can always import from @speckle/shared/dist/** directly
Development
Do yarn build to build or yarn dev to build in watch mode
Code organization
Code should be organized according to areas of speckle, 'core' being the main one. Exports from areas other than "core" should be grouped under namespaces like "RichTextEditor".