-
Notifications
You must be signed in to change notification settings - Fork 1
Develop #541
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
Develop #541
Conversation
✨ feat(Tags.tsx): add ability to create new tags 🔥 chore(useBugDetail.ts): remove unused file 🔧 chore(apiTags.ts): change invalidation tag from 'Tags' to 'Bugs' 🎨 style(BugPreview.tsx): add refetchOnMountOrArgChange to useGetCampaignsByCidBugsAndBidQuery() call 🐛 fix(PageHeader/Tools): useCampaign -> useCampaignBugs ✨ feat(PageHeader/Tools): add useCampaignBugs hook to fetch campaign bugs data
💄 style(Tags.tsx): add eslint-disable-next-line to console.error line
fix(bugs-list): change filters buttons sizes
UN-749-moving-dropdown
Un 535 rtk cache
Recreate design system AppHeader in react
fix(bugs-table): behavior of long use cases
…ng on it ✨ feat(FilterRecap.tsx): add custom status to filter recap and remove it when clicking on it
…atusInfo 🔀 chore(BugsTable): rename getBugStateLabel to getCustomStatusInfo 🔀 chore(types.d.ts): remove unused BugState type definition ✨ feat(BugStateDropdown.tsx): use getCustomStatusInfo instead of getBugStateLabel ✨ feat(BugsTable): use getCustomStatusInfo instead of getBugStateLabel ✨ feat(translation.json): remove unused translations for bug states
…ainer when isFetching is true 🐛 fix(BugPreview.tsx): remove isFetching from the condition to render Skeleton component
…tCampaignsByCidBugsAndBidQuery hook
…r bug statuses and filters
✨ feat(SortBy.tsx): add translation support for sort by labels and refactor to use redux state instead of local state
✨ feat(OrderBy.tsx): add translation support for dropdown items
🔥 refactor(types.d.ts): remove unused OrderSelection type 🚀 chore(bugsPageSlice.ts): remove commented code 🚀 chore(CustomStatusField.tsx): remove commented code and unused imports
UN-795-custom-status-accordion
fix status icon alignment
fix(bugs-table): sort statuses
…ed on isLightbox prop ✨ feat(lightbox.tsx): pass isLightbox prop to DetailsItems component
🎨 style(DetailsItems.tsx): conditionally render BugTags component based on isLightbox prop
New Crowdin updates
New Crowdin updates
…y to Separator component 🎨 style(BugStateDropdown.tsx): change map function parameter name from i to item for clarity 🎨 style(BugStateDropdown.tsx): add space between curly braces and ternary operator in map function
| container: responsive-container / inline-size; | ||
| } | ||
|
|
||
| @container responsive-container (width > 576px) { |
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.
Ma usare una variabile del tema al posto di quel 576? così se un domani dovessimo cambiare i nostri breakpoint non serve andare a modificare pure questi cssoni
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.
Capisco che è un pochino scomodo andare di css variables, ma si può impostare fino a quando non potremo usare la versione aggiornata di styled components. PER LA RELEASE IMMINENTE VA BENE PURE COSI'
| parameters: { | ||
| path: { | ||
| /** Campaign id */ | ||
| cid: string; |
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.
non dovrebbe usare il parametro globale cid?
🐛 fix(BugStateDropdown.tsx): fix key prop warning by adding unique key to Separator component
No description provided.