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

Replaced BottomBar with BottomToolBar #4491

Merged
merged 6 commits into from
Apr 11, 2024

Conversation

Wck-iipi
Copy link
Contributor

Summary

Description of the change(s) you made

Replaced BottomBar with BottomToolBar and removed BottomBar

Manual verification steps performed

I tested the EditModal.vue page, it runs as expected. Also, I ran tests and all passed.

Screenshots (if applicable)

Does this introduce any tech-debt items?


Reviewer guidance

How can a reviewer test these changes?

Please check if StagingTreePage works, I tried finding BottomBar here but couldn't.

Are there any risky areas that deserve extra testing?

References

Fixes #2008

Comments


Contributor's Checklist

PR process:

  • If this is an important user-facing change, PR or related issue the CHANGELOG label been added to this PR. Note: items with this label will be added to the CHANGELOG at a later time
  • If this includes an internal dependency change, a link to the diff is provided
  • The docs label has been added if this introduces a change that needs to be updated in the user docs?
  • If any Python requirements have changed, the updated requirements.txt files also included in this PR
  • Opportunities for using Google Analytics here are noted
  • Migrations are safe for a large db

Studio-specifc:

  • All user-facing strings are translated properly
  • The notranslate class been added to elements that shouldn't be translated by Google Chrome's automatic translation feature (e.g. icons, user-generated text)
  • All UI components are LTR and RTL compliant
  • Views are organized into pages, components, and layouts directories as described in the docs
  • Users' storage used is recalculated properly on any changes to main tree files
  • If there new ways this uses user data that needs to be factored into our Privacy Policy, it has been noted.

Testing:

  • Code is clean and well-commented
  • Contributor has fully tested the PR manually
  • If there are any front-end changes, before/after screenshots are included
  • Critical user journeys are covered by Gherkin stories
  • Any new interactions have been added to the QA Sheet
  • Critical and brittle code paths are covered by unit tests

Reviewer's Checklist

This section is for reviewers to fill out.

  • Automated test coverage is satisfactory
  • PR is fully functional
  • PR has been tested for accessibility regressions
  • External dependency files were updated if necessary (yarn and pip)
  • Documentation is updated
  • Contributor is in AUTHORS.md

@MisRob
Copy link
Member

MisRob commented Mar 29, 2024

Hi @Wck-iipi, thank you for the contribution. I'm sorry for confusion but it's the other bottom bar component that needs to be removed. You can see more here #4351 (comment) and I've just updated the issue description to reflect that #2008

@Wck-iipi
Copy link
Contributor Author

@MisRob I have made the desired changes. I'm sorry I should've looked at previous PR more carefully. I'll be more careful in future.

@MisRob
Copy link
Member

MisRob commented Mar 29, 2024

Oh no, @Wck-iipi, that's on me, this should definitely be mentioned in the issue. We really do not expect anyone to study previous PRs, unless we recommend it for a specific reason. Thank you for your patience and flexibility.

Copy link
Member

@LianaHarris360 LianaHarris360 left a comment

Choose a reason for hiding this comment

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

Hi @Wck-iipi it looks like the linting check is failing. Could you run pre-commit as described in the Kolibri dev docs?

@Wck-iipi
Copy link
Contributor Author

Wck-iipi commented Apr 3, 2024

@LianaHarris360 I have fixed the linting issue

Copy link
Member

@AlexVelezLl AlexVelezLl left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution! In general, code looks good to me, but I have found a couple of things we can improve 👐.

v-if="selecting"
clipped-left
color="white"
flat
data-test="toolbar"
:height="$vuetify.breakpoint.xsOnly ? '72px' : '56px'"
Copy link
Member

Choose a reason for hiding this comment

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

This height prop isnt working now, and this is happening on mobile screens, the bottom bar now doesnt have an appropiate height:

Before:
image

After:
image

One thing we can do is that the BottomBar component receives an appearanceOverrides, where we can pass overrides styles to the bar, and we can end with something like:
<BottomBar :appearanceOverrides=" { height: ... } ">

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have made the desired changes and tested it on the screen above.

width: 100%;
height: 64px;
height: v-bind('appearanceOverrides.height');
Copy link
Member

Choose a reason for hiding this comment

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

Lets have this a little more generic, instead of setting the specific property, we can have this css rule with 64px, but we can pass the appearanceOverrides object to the wrapper div like this:

  <div class="bottom-bar pa-2" :style="appearanceOverrides">
    <slot></slot>
  </div>

This way if the implementers wants to override any other property apart fromm the height can do it without having to update the component.

// eslint-disable-next-line kolibri/vue-no-unused-properties
appearanceOverrides: {
type: Object,
default: () => ({ height: '64px' }),
Copy link
Member

Choose a reason for hiding this comment

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

With the proposed change on the style bellow, this default value will not be required. And this eslint-disable line can be erased too 👐

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@AlexVelezLl I have generalized appearanceOverrides

Copy link
Member

@AlexVelezLl AlexVelezLl left a comment

Choose a reason for hiding this comment

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

Thanks @Wck-iipi! LGTM!

@AlexVelezLl AlexVelezLl merged commit e9935a2 into learningequality:unstable Apr 11, 2024
13 checks passed
@akolson akolson mentioned this pull request Aug 13, 2024
@akolson akolson mentioned this pull request Oct 1, 2024
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.

Duplicate bottom bar components
4 participants