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

Fixed issue where profiles were changing operation type on save #410

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bitskeptic
Copy link

Fixed issue #409 - Profiles created with "Send Broadcast" or "Start Service" operation type revert to "Start Activity" on save. This was occurring because all intent profiles used the IntentOperationData data type and LocalSkillRegistry used this data type to match the profile with a skill. All intent profiles would match against all intent skills, so the first intent skill in the list (which was ActivityOperationSkill) would always be assigned to every intent data type. To fix this issue, new data types were created for all the intent operation skills. Associated DataFactory and SkillViewFragment classes were created as well. The IntentOperationDataTest was also updated. A intent operation utility class was created to house some shared code.

Fixed issue renyuneyun#409 - Profiles created with "Send Broadcast" or "Start Service" operation type revert to "Start Activity" on save. This was occurring because all intent profiles used the IntentOperationData data type and LocalSkillRegistry used this data type to match the profile with a skill. All intent profiles would match against all intent skills, so the first intent skill in the list (which was ActivityOperationSkill) would always be assigned to every intent data type. To fix this issue, new data types were created for all the intent operation skills. Associated DataFactory and SkillViewFragment classes were created as well. The IntentOperationDataTest was also updated. A intent operation utility class was created to house some shared code.
@renyuneyun
Copy link
Owner

Thanks for the PR! Apologise for not responding earlier.

(As mentioned in #401) Is this PR also for #401? If so, there seems to be some conflicts / repeated efforts in trying to fix this: Later down in #401, a commit 17556ca should fix that issue.

@renyuneyun renyuneyun added the fixed? Should have been fixed. Waiting for report. label Apr 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed? Should have been fixed. Waiting for report.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants