-
Notifications
You must be signed in to change notification settings - Fork 530
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
Enhancement: Account Center Updates #1723
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
New dependency changes detected. Learn more about Socket for GitHub ↗︎ 👍 No new dependency issues detected in pull request Bot CommandsTo ignore an alert, reply with a comment starting with Pull request alert summary
📊 Modified Dependency Overview:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should AC be displaying as micro by default?
By adding a bit of z-index to the minimized AC the animation of the Maximized leaving looks a bit cleaner. Doesnt have to be z-index but I think we can clean up that animation a tidbit.
@Adamj1232 added some z-index! I think the animation looks better- good call! |
@@ -1,6 +1,6 @@ | |||
{ | |||
"name": "@web3-onboard/core", | |||
"version": "2.18.1-alpha.2", | |||
"version": "2.18.1-alpha.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is changing the default way core displays I am thinking we should make this a minor version bump
As this is going to change the default behavior for dapps who use account center currently - which could be frustrating - how can we note this change is breaking...Maybe something big on the top of the readme for this specific release(or maybe the next few) with steps to get back to the previous default behavior for AccountCenter (just a code snip of init options for relocating). Any ideas @leightkt @aaronbarnardsound @gesquinca ? |
@Adamj1232 I wouldn't classify this as a breaking change- things will still load, the default location has just changed. But yes we can add instructions for how to reset back to the default location on the release- probably a good idea. |
…onboard into account-center-updates
Sweet, I think it will be helpful! Agreed it won't break the build - unless the have you test for position or layout but breaking changes in ui lib development would also include changes to design systems. The default position to a component would fall under this. As most uses of AC are in the default position this change would break the design of those apps. |
Ahhhhh Super helpful to know! I was thinking of a breaking change in terms of a backend library... but that makes total sense! |
@Adamj1232 yes, this is the plan going forward.
@Adamj1232 100% on this. These changes should be accompanied by some documentation so users can display account center in the old way if they wish to do so. |
@leightkt Seems like we lost the ability to close Account Center panel when clicking outside. We definitely want to keep that. Could you double-check this is the case? |
@Adamj1232 Included a warning at the top of the core readme and the core module page in docs. I figure after a month or so we can move further down the page. ![]() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Nice work!!
This reverts commit 0297ebb.
Description
Update Account Center default location, animation, and position of components.
Loom video of testing
PLEASE NOTE- Checklist must be complete prior to review.
Checklist
package.json
of the package you have made changes in following semantic versioning and using alpha release taggingyarn check-all
to confirm there are not any associated errors(docs update for default position included in kit-docs upgrade)