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

[UI] Button #3

Open
33 tasks done
Tracked by #56 ...
fionataeyang opened this issue Dec 24, 2020 · 3 comments
Open
33 tasks done
Tracked by #56 ...

[UI] Button #3

fionataeyang opened this issue Dec 24, 2020 · 3 comments
Assignees

Comments

@fionataeyang
Copy link
Contributor

fionataeyang commented Dec 24, 2020

@todo

  • implement first iteration of component
    • set up local dev environment with pnpm
      • pnpm link the modules locally
        • pnpm link --global (to make them available)
        • pnpm link --global <./package.json#name>
    • create repository
    • @output 📦 repository
  • refactor component and its dependencies and tag with v0.0.0-prealpha
    • @input 📦 repository
    • refactor very old commit with domlog and old button/icon to use versions
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-prealpha
  • refactor component for last Fiona's commit and tag it with v0.0.0-alpha
    • @input 📦 v0.0.0-prealpha
    • refactor commit with latest terminal/log to use versions
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.0-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.1-alpha
    • @input 📦 v0.0.0-alpha
    • refactor latest commit with latest terminal/log to use versions
    • refactor communication protocol to use latest message standard
    • move terminal/logs to dev dependencies
    • rebase main branch on top of taged version
    • update package.json (new path for the dependencies)
    • update github page links
    • build new bundle.js to include changes in demo page
    • @outputv0.0.1-alpha
  • refactor component latest commit with new comm protocol and tag with v0.0.3-alpha
    • @input 📦 v0.0.2-alpha
    • @outputrepository#v0.0.3-alpha
  • implement next component version v0.0.4-alpha
    • @inputv0.0.3-alpha
    • Button demo (example: text, icon, link, disabled, toggle, switch, navigation)
    • update theming (use stylesheets + allow to send a new stylesheet that overwrites the default one)
    • slim down button component
      • remove cover (image button => should consider making an image component)
      • state only disabled and current
    • document component api in readme
    • install latest dev dependencies
    • update package.json (new path for the dependencies)
    • @output 📦 v0.0.4-alpha

@info

Repo 📂

https://github.com/datdotorg/datdot-ui-button
https://github.com/datdot-ui/link

@fionataeyang fionataeyang self-assigned this Dec 24, 2020
This was referenced Dec 24, 2020
@serapath serapath mentioned this issue Feb 17, 2021
6 tasks
@serapath serapath mentioned this issue Mar 7, 2021
14 tasks
@serapath
Copy link
Member

serapath commented Mar 7, 2021

Button

image

@serapath
Copy link
Member

@ninabreznik
worklog 2022.04.07 - locking UI elements

Notes:

  • v.0.0.1-alpha: ui elements, updated to use new comm protocol
  • 0.0.0-alpha: ui elements in the original Fiona's state (only a few)
  • tab component has since moved into button component (under tab is old version, under button is many types of buttons, including the tab). When we start refactoring (splitting/merging components), we can see what to do here. I made a comment in the issues:

Results:

v0.0.1-alpha (using new comm proto)

0.0.0-alpha (old/Fiona's original)

This was referenced Apr 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants