Adam Hathcock
1ac972f02a
* first pass of CLI ifc converter * some updates * closer * yarn works * can execute ifc? * change exe * remove extra venv needs * invocation works * fixed dockerfile and url * refactor(fileimport): temp results path should not be hardcoded in parsers * update importer to output stuff * fix up argments * remove dead code * adjust dockerfile to have tini and workdir better * fix node to a specific version * Add shell statement and pin yarn version * add ifc converter c# to ignore * merge fix * move ifc c# * fix the api usage * update the importer to new SDK * Adds a feature flag `FF_FILEIMPORT_IFC_DOTNET_ENABLED` for enabling .Net IFC parser * move directories * put back ifc js * use FF and reversions * needs token too * fix docker? * one last copy fix * adjust prettier ignore * change to enable * fix helm chart nesting * Amend healthcheck node binary path * Add FF_FILEIMPORT_IFC_DOTNET_ENABLED to feature flag parser * Allow app to write to /.config directory * fix: volume name has to be lower case * update ifc importing --------- Co-authored-by: Iain Sproat <68657+iainsproat@users.noreply.github.com> Co-authored-by: root <root@Clynelish>
@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".