Closed Bug 1014442 Opened 10 years ago Closed 9 years ago

[Settings] refactor Find My Device panel with AMD pattern

Categories

(Firefox OS Graveyard :: FindMyDevice, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:-)

RESOLVED FIXED
blocking-b2g -

People

(Reporter: gasolin, Assigned: scottwu)

References

Details

Attachments

(1 file)

Overview Description:

Refactor Find My Device panel with AMD pattern referring to
https://github.com/gasolin/gaia/tree/master/apps/settings

to make it modularize and more easier to maintain


Expected Results:

pass all settings test and act the same as original implementation

Additional Information:
Component: Gaia::Settings → FindMyDevice
Fred, is this a blocker?
blocking-b2g: --- → 2.0?
Flags: needinfo?(gasolin)
blocking-b2g: 2.0? → ---
I can't imagine a refactor being a blocker.
Sounds good. I've tagged for backlog.
Flags: needinfo?(gasolin)
Whiteboard: backlog-2.1
It shall be in engineer task queue but not a blocker
[Blocking Requested - why for this release]:
blocking-b2g: --- → 2.1?
Whiteboard: backlog-2.1
Removing the nomination, I don't really think optional stuff like refactoring should block until we have more devs on this project
blocking-b2g: 2.1? → ---
agree, this isnt a 2.1 blocker.   minusing.
blocking-b2g: --- → -
Assignee: nobody → scwwu
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

Made some changes to the structure and unit test. Please let me know what you think. Thank!
Attachment #8662190 - Flags: review?(gasolin)
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

also add lissyx for functionality check since he is 'Find My Device' peer
Attachment #8662190 - Flags: review?(lissyx+mozillians)
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

Looks good but I fear we are going to leak observers.
Attachment #8662190 - Flags: review?(lissyx+mozillians)
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

Thanks for working on the patch. 
Please address the comments on github then set review again.
Attachment #8662190 - Flags: review?(gasolin)
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

Sorry for taking this long to fix the code. I believe I've fixed all the suggestions. Please let me know if you catch any other mistake. Thanks!
Attachment #8662190 - Flags: review?(gasolin)
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

Looks good and works on device. Thanks Scott!

Add @lissyx in review queue. Please land after @lissyx feel its ready
Attachment #8662190 - Flags: review?(lissyx+mozillians)
Attachment #8662190 - Flags: review?(gasolin)
Attachment #8662190 - Flags: review+
Comment on attachment 8662190 [details] [review]
[gaia] scottwu:1014442-refactor-find-my-device-with-amd > mozilla-b2g:master

Please be extra cautious and make sure you are not introducing any mozSettings observer leaks in your SettingsListener/SettingsHelper use: I have not saw anything wrong but I might be missing them because of AMD.

So any .observe() should be unobserve()'d. There are silent addObserver() call being made by SettingsListener/SettingsHelper when you create those objects, do you need to make sure you have the proper balance or do not constantly recreate thoes objects.
Attachment #8662190 - Flags: review?(lissyx+mozillians) → review+
Got it. Thanks for the reminder Alexandre. I'll be extra careful when dealing with observers.

I've fixed the line break tissue. Thanks Fred!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: