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

4.x button updates #716

Merged
merged 15 commits into from
Jul 7, 2022
Merged

4.x button updates #716

merged 15 commits into from
Jul 7, 2022

Conversation

GaryRidgway
Copy link
Contributor

@GaryRidgway GaryRidgway commented Jun 27, 2022

Resolves #706
Resolves #710

To test

  • check to see that the transparent option is present, and that the transparent borderless option has link underlining.
  • test that going to font awesome and copying an icon (An example icon is here, copy everything in the <i> tag)
  • Test that the full width option is available and working properly
  • check that the borderless option works for both the card and button
  • Test background color combinations, if possible 4.x button updates #716 (comment)

@GaryRidgway GaryRidgway changed the base branch from 3.x to 4.x June 27, 2022 21:15
@GaryRidgway GaryRidgway self-assigned this Jun 27, 2022
@pyrello
Copy link
Contributor

pyrello commented Jun 28, 2022

@GaryRidgway It seems like the last thing you need to do here is write up testing instructions.

@GaryRidgway GaryRidgway linked an issue Jun 28, 2022 that may be closed by this pull request
5 tasks
@quamsta
Copy link

quamsta commented Jun 29, 2022

I'll likely do a test run on adding this to the Brand Icon Browser today, not sure if that counts as a full review, but I'll put anything of note in here.

@quamsta
Copy link

quamsta commented Jun 29, 2022

@pyrello , @GaryRidgway does the building/compiling of the uids module's dist/ folder happen during a GitHub action? I attempted to import the components in the Brand Icon Browser, but I quickly realized that the statement I was using:

import { UidsBrandBar, UidsButton } from "uids";

...was still importing the old version of the UidsButton component. Does the dist/ folder need to be built in the 4.x-button-updates branch or will it happen automatically when it's merged into 4.x?

@pyrello
Copy link
Contributor

pyrello commented Jun 29, 2022

@quamsta This process is not automated yet :|

Here is the relevant issue: #100. Running yarn build should take care of it. Sorry we forgot to do this the other day.

@quamsta
Copy link

quamsta commented Jun 29, 2022

@pyrello All good! I attempted to run yarn install and yarn build within Icon Browser's node_modules/uids folder, which did succeed, but upon trying to use the components, I received this error:

app.js:1201 Uncaught TypeError: Cannot read properties of null (reading 'isCE')
    at renderSlot (runtime-core.esm-bundler.js?9feb:2947:1)
    at Proxy._sfc_render (uids.es.js?175d:1:1)
    at renderComponentRoot (runtime-core.esm-bundler.js?d2dd:895:1)
    at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js?d2dd:5059:1)
    at ReactiveEffect.run (reactivity.esm-bundler.js?89dc:185:1)
    at setupRenderEffect (runtime-core.esm-bundler.js?d2dd:5185:1)
    at mountComponent (runtime-core.esm-bundler.js?d2dd:4968:1)
    at processComponent (runtime-core.esm-bundler.js?d2dd:4926:1)
    at patch (runtime-core.esm-bundler.js?d2dd:4518:1)
    at mountChildren (runtime-core.esm-bundler.js?d2dd:4714:1)

Which I Googled around for and found this post from: vuejs/core#4344

That's because you have two distinct copies of the Vue package being used, one in each package.

Vue uses a global singleton to track the current rendering instance - having more than one copy included will inevitably lead to such issues.

So I assumed I somehow duplicated or otherwise blew up my local UIDS components/package by attempting to run yarn build inside of node_modules, but I'm not sure.

@bspeare
Copy link
Contributor

bspeare commented Jun 29, 2022

Changes that need to be documented

  • The major change in this that we need capture in our changelog is that buttons using bttn bttn--outline bttn--tertiary like on https://tippie.uiowa.edu/kira-price-story-undergraduate will render with a white background instead of being transparent. The button classes would need to be changed to bttn bttn--transparent like on https://tippie.uiowa.edu/iowa-mba/curriculum/dual-degrees where the sections alternate between background colors.
  • Additionally, we will need to change the default card button classes to bttn bttn--transparent bttn--sans-serif.
  • bttn__apply has been removed.
  • bttn__link has been removed bttn borderless bttn--transparent bttn--sans-serif should be used as a replacement.

@bspeare
Copy link
Contributor

bspeare commented Jun 29, 2022

Can we figure out a way to test these buttons with multiple background classes in this pr? I've been working with https://uids.brand.uiowa.edu/branches/feature_button_tertiary_fixes/components/preview/kitchen-sink.html to test, but it is not ideal.

@bspeare
Copy link
Contributor

bspeare commented Jun 29, 2022

Should we add #714 to _border.scss here?

@bspeare
Copy link
Contributor

bspeare commented Jun 29, 2022

@pyrello
Copy link
Contributor

pyrello commented Jun 30, 2022

bttn--apply has been removed. It is only used in viewbooks and perhaps we should move it to https://github.com/uiowa/vuejs-site-template?

What is bttn--apply doing?

@bspeare
Copy link
Contributor

bspeare commented Jun 30, 2022

I thought it was used in the viewbooks but I guess not. I would guess I added it for a uiowa.edu header button that is no longer in use.

@GaryRidgway
Copy link
Contributor Author

Screen Shot 2022-06-30 at 10 08 47 AM
it is used on viewbooks to add the proper icon to an apply button
this is live on the admissions viewbook

@GaryRidgway
Copy link
Contributor Author

it serves the same functionality as bttn--visit, bttn--ask, and bttn--connect

@bspeare
Copy link
Contributor

bspeare commented Jun 30, 2022

@GaryRidgway I updated the class name in #716 (comment). It is a different class than the viewbook example.

@bspeare
Copy link
Contributor

bspeare commented Jun 30, 2022

I removed the BEM nesting and also removed the bttn--link modifier and added a entry for it in #716 (comment).

@GaryRidgway
Copy link
Contributor Author

GaryRidgway commented Jun 30, 2022

Future work:

  • remove medium option
  • add the option to align the icon left.
  • remove serif option

@bspeare
Copy link
Contributor

bspeare commented Jun 30, 2022

Should we remove this serif option?

Screen Shot 2022-06-30 at 1 11 17 PM

quamsta
quamsta previously approved these changes Jul 5, 2022
Copy link

@quamsta quamsta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey all, these buttons are looking pretty fresh. I was able to use the latest commit from this branch in the Icon Browser and tested several variations and they're all looking pretty nice, landed on tertiary, small:

Screen Shot 2022-07-05 at 11 03 50 AM

Screen Shot 2022-07-05 at 11 04 01 AM

I'm going to approve this since it looks great on my end, but anyone should feel free to add their own review/approval here before this gets merged. Thanks everyone!

@pyrello
Copy link
Contributor

pyrello commented Jul 5, 2022

Should we remove this serif option?

I thought we specifically decided to add that. Do you want to not have it anymore?

@bspeare
Copy link
Contributor

bspeare commented Jul 5, 2022

@pyrello I don't see us using the serif font any time soon. Maybe we could shelve it for now?

Copy link

@quamsta quamsta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving this because apparently my old review got stale!

@GaryRidgway GaryRidgway merged commit d9f64e5 into 4.x Jul 7, 2022
@GaryRidgway GaryRidgway deleted the 4.x-button-updates branch July 7, 2022 14:14
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

Successfully merging this pull request may close these issues.

4.x - Button component updates
4 participants