feat: Index dropdown field option for toolbox-search

[sammitako]

The basics

• I validated my changes

The details

Resolves

Partially addresses
#1940

Proposed Changes

When indexing blocks, check if a field is a dropdown, and index the text value and ImageProperties value of their options.

Reason for Changes

When the block has a dropdown option, other than the default one, the hidden values in the options are not searchable.

Test Coverage

Manually test only.

Documentation

No.

Additional Information

Collaborated with https://github.com/ludizhan

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[humera811]

I faced a similar linting issue. You can try
git commit --amend -m "fix: Update toolbox-search to search dropdown field options"
git push --force origin osd

[humera811]

I faced a similar linting issue. You can try git commit --amend -m "fix: Update toolbox-search to search dropdown field options" git push --force origin osd

fix instead of Fix

[ludizhan]

@humera811 @sammitako There are 3 commits in this PR, the issue is probably caused by the other commits in the PR.

Can you try this?

• git rebase -i HEAD~3 Enter interactive rebase mode for the 3 most recent commits
• Replace pick with reword for the commit that doesn't start with fix: or feat:
  • Basically replace the first line pick f5822adf Index dropdown field option for toolbox-search -> reword f5822adf Index dropdown field option for toolbox-search
  • The allows you to update the commit message
• Modify the commit message to fix: Index dropdown field option for toolbox-search
• After saving, you should exit the interactive rebase mode
• git push --force origin osd

[ludizhan]

Note: This actually partially fixes #1940

There were 2 steps stated in the original issue about how to fix it, and this completes and first step.

We intend to follow up with another PR later to complete the second step, as well as adding unit tests.

[johnnesky]

Thanks for the hard work everyone! I look forward to part 2 of this issue!