4290/search buildings

[aidanhenry]

Description

This adds the search feature which was accidentally missing from previous PR. I have done my best to avoid running in to the same issues that the previous PR had. This was feature was based on the existing event search feature, but simplified. I do not see any new errors.

Fixes #4290

Review Time Estimate

Please give your idea of how soon this pull request needs to be reviewed by selecting one of the options below. This can be based on the criticality of the issue at hand and/or other relevant factors.

• [x] Immediately
• [ ] Within a week
• [ ] When possible

Type of changes

Please select a relevant option:

• [ ] Bug fix (non-breaking change which fixes an issue).
• [x] New feature (non-breaking change which adds functionality).
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
• [ ] Other (any another change that does not fall in one of the above categories.)

Checklist:

Please select all applicable options:

• [ ] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
• [ ] I have updated the CHANGELOG.
• [ ] I have read the Contributor Guidelines.
• [ ] I have performed a self-review of my own code.
• [ ] I have commented my code, particularly in hard-to-understand areas.
• [ ] My change requires updating the documentation.
• [ ] I have made necessary changes to the documentation.
• [ ] I have added tests related to my changes.
• [ ] My changes generate no new warnings.
• [ ] New and existing unit tests pass locally with my changes.
• [ ] Any dependent changes have been merged and published in downstream modules.

---

[aidanhenry]

It looks like I'm many commits ahead of the support branch. What's the best way to get this synced up?

[mihail-varbanov]

Just merge the current content of support/v6.0 branch to your 4290/search-buildings branch before creating the PR.

Update: This is valid only if 4290/search-buildings branch was created as a fork from support/v6.0, please see my next comment for details.

[mihail-varbanov]

Did you create 4290/search-buildings branch as a fork from develop branch? If yes, this was wrong and you have to create a brand new branch from current support/v6.0, then add your updates related to #4290, and then create new PR for these changes targeting support/v6.0.

The current develop branch contains features that will appear in the future 6.1 release. If your 4290/search-buildings is based on develop, merging your PR to support/v6.0 will also add the 6.1 features to the upcoming 6.0 hot fix release, that would be very very wrong.

[aidanhenry]

Closing this PR to reopen it from a branch forked from support/v6.0