@lca_platform/assembly

LCA Collect - Shared Assembly Library

A shared library for assembly related components and pages. This library contains components that can be used to deal with assemblies and EPDs.

Getting Started

npm install

Build, Test & Publish

Testing is done with Vitest

npm run test

To add a new component:

• Add a folder containing the new component (remember to follow naming conventions)
• Add an export in the src/components/index.ts

To publish a new version:

• Update the version in package.json (remember to follow semver)
• When you're satisfied and ready to publish, then create a PR

Development Setup with other @lca_platform packages

You can use npm link to set up live reloading of the other @lca_platform packages.

• Clone the package that you wish to enable live reload on.
• In the terminal, go the root folder of the cloned repo and write npm link in the terminal
• Go back to this repo's root folder and write npm link @lca_platform/{PACKAGE} to link the package.
• When you make changes to the package, that you wish to see in this app, simply run npm run build in the package and the changes will available here.

Folder Structure and Naming

src/ # Contains the source code and components
    __mocks__/ # Contains the mock data and functions for unit tests
    components/ # React components
        myComponent/ # Each component has its own folder
            index.ts # Export of what is public
            myComponent.tsx # The component
            myComponent.spec.tsx # Unit test file
    dataAccess/ # Apollo Client folder
        generated.ts # Autogenerated file from Apollo with React Hooks for data fetching
        schema.graphql # File for writing GraphQL queries

Further Documentation

Further documentation for LCAPlatform can be found here

License

Unless otherwise described, the code in this repository is licensed under the Apache-2.0 License. Please note that some modules, extensions or code herein might be otherwise licensed. This is indicated either in the root of the containing folder under a different license file, or in the respective file's header. If you have any questions, don't hesitate to get in touch with us via email.