docs: Deprecate TapDetector in favour of TapCallbacks#2886
Conversation
Update t-rex game to use `TapCallbacks` instead of `TapDetector`, in anticipation of [deprecating the latter](#2886). Also update the term high score to avoid a dictionary entry. Co-authored-by: Lukas Klingsbo <[email protected]>
|
@luanpotter what were our concerns here again? I think it would be great to only have |
|
@spydon see my design doc for complete breakdown |
Where is the design doc? Would be good to have that linked here so that we can have a look at it every 6 months after we've forgotten what it's about. 😄 |
|
@spydon should I reactivate this now that we have agreed on moving forward with this? |
Did you get a green light from @erickzanardo too? Because I think he was the one that was sceptical. Otherwise it sounds good to me! |
4ebc8f9 to
87453b3
Compare
87453b3 to
aba91cd
Compare
|
@spydon @erickzanardo are we able to finally move forward with this and kickstart the event system migration as outlined on my doc? |
|
lmk if we prefer to split the fixes into a separate pr first - I didn't realize the old system was used so much across the codebase |
Sure, let's go! |
|
@spydon - @renancaraujo has very strong opinions on whether games should use tap up or tap down listeners, but I always forget what is the "standard". I will let him follow up unifying all examples that don't care to his preferred standard :) |
Description
Deprecate
TapDetectorin favour ofTapCallbacksChecklist
docsand added dartdoc comments with///.examplesordocs.Breaking Change?