Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Meta] 2022 Roadmap #5468

Closed
9 of 16 tasks
thompsongl opened this issue Dec 14, 2021 · 5 comments
Closed
9 of 16 tasks

[Meta] 2022 Roadmap #5468

thompsongl opened this issue Dec 14, 2021 · 5 comments
Labels

Comments

@thompsongl
Copy link
Contributor

thompsongl commented Dec 14, 2021

🗺️ 2022

2021: #4054

Top Projects

Modularization

Theming & CSS-in-JS

Monorepo setup

Empty states

Data grid support

Refactors

Testing

  • More Cypress
  • Downstream project deployment (e.g., a-la-carte)

Infra

  • Release via Jenkins

In-product help

Documentation

  • Navigation levels, searching, and deep-linking improvements

EuiMarkdownEditor

@thompsongl thompsongl pinned this issue Dec 14, 2021
@snide
Copy link
Contributor

snide commented Dec 16, 2021

Two component requests that are coming from downstream work in design that I'd like to fit in here. Both of these we should spec out in design first.

  • We need a standardized way to provide @reply and #search functionality into textareas like EuiMarkdownEditor with a clean syntax.
  • A sticky component that takes into account our various headers, bottom bars.

@eduardolandaiqmetrix
Copy link

Hey Guys! Quick question, is there any update on when a new update will be available on production/master to have CSS-JS instead of SASS? :)

@miukimiu
Copy link
Contributor

@eduardolandaiqmetrix the CSS-in-JS efforts already started. It's a work in progress. You can follow the meta issue here: #3912.

@thompsongl thompsongl changed the title [WIP] 2022 Roadmap [Meta] 2022 Roadmap Jan 18, 2022
@miukimiu
Copy link
Contributor

We need a standardized way to provide @reply and #search functionality into textareas like EuiMarkdownEditor with a clean syntax.

@snide we opened a discussion #5829 and created an internal spec doc to start tackling this issue.

@JasonStoltz JasonStoltz unpinned this issue Feb 2, 2023
@JasonStoltz
Copy link
Member

I'm closing this issue. We'll be working on a 2023 Roadmap next week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants