Closed differsthecat closed 2 years ago
I am aware of the build issue here. Devops has a potential fix, but I think this is an anomaly with this branch that may self correct. I don't think it should hold up merging, considering the target branch doesn't build anyway :)
Update: Oscar knew what was going on here and fixed the build
@addisonbeck The reason it doesn't build is due to there being a package in package-lock
that gets put in jslib. This often happens when someone bumps jslib packages and forget to refresh the client. (It should go away with the move to monorepo)
For now, recreate package-lock, if it still fails check which package it attempts to to drag in, and copy it to package.json
.
Found the issue, seems jslib/common wanted node-forge 1.3.1, and web for some reason resolved it to 1.3.0. I hard coded web to use the latest for now, the move to mono repo should resolve this permanently.
Latest commit: |
307417b
|
Status: | ✅ Deploy successful! |
Preview URL: | https://0ea4ade3.web-46f.pages.dev |
https://bitwarden.atlassian.net/browse/SG-16
Type of change
Objective
The product initiative here is to implement the filters section of the end user vault refresh epic. This includes:
There are some other initiatives in here, mostly around refactoring. These include:
VaultModule
withIndividualVaultModule
andOrganizationVaultModule
children that share a service. This is to share search field placeholder text logic between the org and individual vault components. There is certainly a lot more that could be shared between these two and refactored, but this already seemed like scope creep and only went far enough to achieve the need for filters.Code changes
GroupingsComponent
into aVaultFiltersModule
with components for each filter typeOrganizationFilterComponent
<a>
tag with aclick
event that performed the filter, but that<a>
tag could have any number of<span>
or<i>
tags inside of it that had their own click events. I changed all of this so every clickable element is a<button>
, and added the attributes requested by design.VaultModule
withIndividualVaultModule
andOrganizationVaultModule
children that share a service.SharedModule
for passing shared code around to feature modulesLooseComponentsModule
as a temporary space for homeless components to exist and be consumed by feature modules.Screenshots
Before you submit
npm run lint
) (required)