cc-logs-application-view: add a fullscreen button mode (d6c7e36), closes #983
cc-logs-application-view: init component (732b48e), closes #967
cc-logs-control: add header slot (9fcbff6), closes #964
cc-logs-instances: add tooltips to commit label and instance index (438751c)
cc-logs,cc-logs-control: add the ability to filter on logs' message (362c9ba)
cc-popover: add --cc-popover-trigger-button-width css property (3e1dc1c)
cc-smart-container: allow optional property in smart context (c62f172)

🐛 Bug Fixes

cc-input-date: fix date formatting at midnight (bc67946)
cc-logs-application-view: fix loading message visibility hover black theme (ba1e0b4), closes #1019
cc-logs-control: fix the event detail when metadata-display option changes (222e110)
cc-logs-instances: fix instance selection (3ff0206)
cc-logs-instances: fix sort order of the instances when grouped by deployments (0bb4d18)
cc-logs-instances: fix spacing around deployment relative date (7a95572), closes #965
cc-logs: do not collapse spaces in log messages (90f3d9f), closes #965
cc-logs: do not include hidden metadata into clipboard (ca7cacb)
cc-logs: fix spacing between metadata and message (a7534ef)

Readme

Source

title: 'Readme'

Collection of Web Components by Clever Cloud

What is this?

This project contains a collection of Web Components made by Clever Cloud.

Some of those components are low-level like <cc-button>, <cc-input-text> or <cc-loader>, the other components are more high-level and specific to Clever Cloud's domain model.

We use them on different Web UIs we have (public and internal).

Why is it public?

We want to share our knowledge and experience with Web Components along with the tooling we used to build them. We hope it will help others for their own components.
We use those components ourselves but we also want our clients and partners to use them in their own custom Web UIs based on our products.
We think it's a great way for our clients to give feedbacks (and even contributions) on small parts of our Web UIs.

Can I see those components?

All our components are showcased with "stories" using Storybook. You can see all our components (and their stories) on this preview.

Storybook is a great tool to present your components in many different situations. This way, you can check how they behave with different inputs (properties, attributes...) and make sure they produce the right outputs (emit events...).

We also use web-component-analyzer to generate a documentation spec sheet for each component. You can find it in the Notes tab of a component's story (example).

Can I use them in my project?

Sure, they're available on npm. Contact us if you want more details.

License

This project is licensed under the Apache-2.0.

We're using modified versions of two projects related to Leaflet:

Both projects are licensed with BSD-2-Clause. They aren't updated anymore, and we wanted them to be exposed as modern ES modules. This is the main reason we decided to copy them in our own repo. The respective copyrights are at the top of each file:

src/lib/leaflet-heat.js
src/lib/simpleheat.js

Icons are powered by Remix Icon.

Keywords

FAQs

What is @clevercloud/components?

Is @clevercloud/components popular?

Is @clevercloud/components well maintained?

Last updated on 12 Apr 2024

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install