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

TagsSelector undo feature #82

Merged
merged 6 commits into from
Sep 30, 2021
Merged

TagsSelector undo feature #82

merged 6 commits into from
Sep 30, 2021

Conversation

mdrlzy
Copy link
Member

@mdrlzy mdrlzy commented Sep 27, 2021

#18

Copy link
Member

@kirillt kirillt left a comment

Choose a reason for hiding this comment

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

It works. Small detail to fix and we can merge it.


private fun verifyActions() {
if (storage == null || index == null)
return
Copy link
Member

Choose a reason for hiding this comment

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

Is it probable case that storage or index are nulls? If it is possible only in case of a bug, then throw AssertionError("detailed message") should be used.

Copy link
Member Author

Choose a reason for hiding this comment

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

storage and index are null's while indexing is in progress and the user can tap "back"
But we handle this case by checking actions.isEmpty()

Copy link
Member

Choose a reason for hiding this comment

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

If we handle this case in other place (onBackClick() IIUC), then this return is confusing since we never reach it in fact. I would replace it with AssertionError then to catch a bug if we are wrong. Technically, we need to put it only for debug mode, but at this stage of project we don't really have production :)

@kirillt
Copy link
Member

kirillt commented Sep 27, 2021

Let's add #83 into this PR (resources-grid-perfomance branch)

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.

None yet

2 participants