-
-
Notifications
You must be signed in to change notification settings - Fork 180
[WIP] New mockup with vuex #91
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
Conversation
Signed-off-by: Olga Bulat <obulat@gmail.com>
Convert Help buttons into links; render links using 'modals' object and v-for loop Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
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.
It's nice to see lots of defunct components being cleaned up!
Some specific things:
- Now that the vertical stepper is the stepper, I think it would make sense to rename it simply to "Stepper", or "Steps", then renaming the VerticalStep component to simply "Step", or something like this.
- The store still needs to be moved to
./src/store/index.jsfrom./store/index.js - It seems to make more sense to me to have the Stepper component manage the
stepsarray that is currently in state, additionally, moving theenabledAndVisibleStepsarray to the Stepper component. Is there a reason that they are managed by the state? Are these arrays used only by the stepper and its children, or by other components? - I'm seeing some choppy behavior when transitioning between selected steps. This may be due to now using VueX bindings for changing selected step instead of having the VerticalStepper component itself manage this. The update to the state would take time to propagate, thus making the transitions choppy.
Overall, looks good! I think it would be good to move more stuff from the store into the VerticalStepper component. A good test would be to ask yourself if the information or method in the store is only used by the stepper, or its children. If it is, it's probably good to move it out of store. In general, I think of the purpose of store as being to track data and global state, not manage behavior - that's for components.
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
Signed-off-by: Olga Bulat <obulat@gmail.com>
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 much better! I like how slim the state is now, I think "the division of labor" makes much more sense.
There are a number of text and styling differences between this branch and the Figma, but I assume these will be taken care of in a subsequent PR. Go ahead and merge whenever :)
Signed-off-by: Olga Bulat <obulat@gmail.com>
Description
New design is implemented, including new VerticalStepper component for Stepper.
Data shared among various components is moved to vuex store for easier handling.
Other information
Checklist:
Update index.md).masterbranch of the repository.visible errors.
Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.