Skip to content

Remove or update experimental components #315

@maxatdetroit

Description

@maxatdetroit

These changes will be included in a 3.0.0-alpha release so it can be deployed in the detroitmi 3.0 (i.e. newdetroitmi) theme in Drupal without waiting to migrate the usage of these components across all the places they're used (see code search results below + there are usage of these components in the CMS DB via the HTML editor).

This will also allow us to continue releasing new components / bug fixes on the 2.X version branch while finishing this issue.

Note some of this was already done in 2.0.0-alpha1 branch.

Components to Remove

We're removing these because we don't want to maintain them in the DS moving forward. Each of these components either:

  • is built using trivial HTML/CSS (in which case they should be implemented outside the DS)
  • can be replaced with another component once the other component uses slots/CSS parts/custom CSS properties
  • is not used and we don't expect it to be used
  • is very buggy / there is no immediate use and should be rewritten and added back at a later time

Components:

Components to Update/Rewrite

We're updating these because we want to maintain them in the DS long-term anyway. Note: 'updating/rewriting' may entail removing the component from the DS for an indefinite period of time before building it from scratch in the future, or it may mean rewriting the API entirely on the next major release.

Components:

Components to Move to Stable (now)

Metadata

Metadata

Assignees

No one assigned

    Labels

    cleanupmajorIncrement the major version when merged

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions