equinor / equinor/design-system

Create custom code components for Power Platform

Open
#2,425 5 comments 0 reactions 1 assignee Assigned to @Hjaf View on GitHub
🛑 on hold power apps power platform
Dominant language
TypeScript
Stars
151
Forks
75
Avg merge
2d 11h
Merged PRs (30d)
38

Description

Adding support for the component framework can help avoid technical debt and maintenance as this will be common for multiple Power Platform elements, as opposed to [traditional components](#1967 ) which is only useable in Canvas Apps.

[Component framework](https://docs.microsoft.com/en-us/power-apps/developer/component-framework/overview)

## Development

### Resources

https://learn.microsoft.com/en-us/power-platform/developer/cli/reference/pcf

https://github.com/microsoft/powercat-code-components

https://github.com/microsoft/PowerApps-Samples

https://pcf.gallery/

### Environment

[EDS Dev](https://make.powerapps.com/environments/2c26a774-49a8-4666-9eae-968f48d2ad03/home)

### Deployment

> We should perhaps put the PCF components in the [EDSPowerPlatform](https://github.com/equinor/EDSPowerPlatform)
repository and using actions in this repository for building and deploying components.

## Users

Important to remember that the users of PCF components are the citizen developers and not their end users, this is covered by the core component. We should try our best to adhere to conventions used by Microsoft. e.g. the order of parameters.

## Tasks

- [ ] Create PCF components
> See list under components for priority
- [ ] CI/CD for code-components
> essentially we should deploy this to any environment in our tenant where code components are enabled. for now we stick to deploying these to the [EDS Dev](https://make.powerapps.com/environments/2c26a774-49a8-4666-9eae-968f48d2ad03/home) environment
- https://github.com/equinor/EDSPowerPlatform/issues/61
- [ ] Align meta for equinor/design-system and equinor/EDSPowerPlatform (labels, status etc)

## Components

### User testing

Start out with components cannot be replicated by configuring native controls (e.g. labels) and make them available for testing

- [x] [Button](https://www.figma.com/files/682286909510540417/project/89864877/EDS-2.0-preview?fuid=633938568252624013)
- [ ] [Autocomplete](https://github.com/equinor/EDSPowerPlatform/issues/51)
- [ ] ~[Datepicker](https://eds.equinor.com/0b0c666ab/p/07b531-datetime-picker/b/86826a)~
- [ ] [Table](https://eds.equinor.com/0b0c666ab/p/392109-table/b/398446)
- [ ] [Sidebar](https://eds.equinor.com/0b0c666ab/p/10f83e-sidebar/b/887642)
- [ ] [Snackbar](https://eds.equinor.com/0b0c666ab/p/626020-snackbar/b/15cfd0)
- [ ] [Chip](https://eds.equinor.com/0b0c666ab/p/95e67f-chip/b/398446)
- [ ] ...

### Publishing

Make the PCF components and documentation available, either by making [equinor/EDSPowerPlatform](https://github.com/equinor/EDSPowerPlatform/) and publishing documentation in its own GitHub page, or merge relevant code into [equinor/design-system](https://github.com/equinor/design-system/)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.