Skip to content

Added actions from #57321 to the 'No Settings Found'-message#59739

Merged
roblourens merged 3 commits intomicrosoft:masterfrom
NiclasvanEyk:master
Oct 5, 2018
Merged

Added actions from #57321 to the 'No Settings Found'-message#59739
roblourens merged 3 commits intomicrosoft:masterfrom
NiclasvanEyk:master

Conversation

@NiclasvanEyk
Copy link
Contributor

This PR contains a first suggestion for adding the two actions for clearing all filters and clearing the search to the 'No Settings Found'-message on the settings-search as described in #57321.

The first one is only shown, if there are actually any filters active. The second one is always shown.
I am not sure how to deal with the translations here, since I was not able to find similar, already translated texts I added new ones. If this is not the correct way, please help me here.

As I am new to the codebase I am also not sure, whether the approach with the disposables array is the right one. Is there any documentation about the life cycle of the editor parts available?

@msftclas
Copy link

msftclas commented Oct 1, 2018

CLA assistant check
All CLA requirements met.

@roblourens roblourens added this to the October 2018 milestone Oct 1, 2018
import { IPreferencesService, ISearchResult, ISettingsEditorModel, ISettingsEditorOptions, SettingsEditorOptions, SettingValueType } from 'vs/workbench/services/preferences/common/preferences';
import { SettingsEditor2Input } from 'vs/workbench/services/preferences/common/preferencesEditorInput';
import { Settings2EditorModel } from 'vs/workbench/services/preferences/common/preferencesModels';
import { Disposable } from 'vscode';
Copy link
Member

Choose a reason for hiding this comment

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

Don't import from 'vscode' here, that module is for extensions. You can use IDisposable from lifecycle.ts

Copy link
Member

Choose a reason for hiding this comment

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

Actually you don't need to add that array because SettingsEditor2 already extends Disposable, the _register method adds disposable objects to its internal set of disposables.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks for pointing me in the right direction. I removed the import and replaced the array-logic with calls to _register

parsedQuery.tags.forEach(tag => this.viewState.tagFilters.add(tag));

// show or hide 'Clear Filters'-link
this.clearFilterLinkContainer.style.display = this.viewState.tagFilters.size > 0
Copy link
Member

Choose a reason for hiding this comment

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

Maybe this should go in renderResultCountMessages?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, this seems like a more appropriate place for this logic. I moved it.

The previous solution involved an own solution with an array of
disposables. The new solution makes use of the _register-method from the
Displosable class.
Copy link
Member

@roblourens roblourens left a comment

Choose a reason for hiding this comment

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

Looks great, thanks!

@roblourens roblourens merged commit 866c6d6 into microsoft:master Oct 5, 2018
@github-actions github-actions bot locked and limited conversation to collaborators Mar 27, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants