Improve Core Code Quality from Svelte Warnings #3563
Labels
internal
Stuff like NFRs, CI pipeline
refactoring
Something needs to be refactored in a separate task
After introducing Vite we get nice warnings about new svelte code recomendations when running
npm run build
incore/
We might as well solve these issues to avoid having these warnings there instead of just enforcing a non-verbose vite build.
Looking at the warnings a lot of them are very small suggestions, that shouldn't do any harm. So we can start from the easier ones.
Following is generated summary that is more legible and helps to separate these issue into mini-tasks:
Note: Lots of good first issues can come out of this.
In issues for which the warnings make no sense for our use case, need to develop a solution, simple enough to disable the warnings if it just makes no sense. ex: "Unused export property" issues might be one of them.
Accessibility Issues (72 Issues):
<a>
element should have an href attributeUnused CSS Selectors (17 Occurrences):
Unused exports (7 Issues):
export const urlAuthError
export const userSettingsGroupKey
export const schemaObj
export const displayCustomSearchResult
export const displayCustomSearchResult
export const hideNavComponent
+ Breadcrumb has unused export property 'responsiveNavSetting'. If it is for external reference only, please consider usingexport const responsiveNavSetting
Total Issues: 16
The text was updated successfully, but these errors were encountered: