fix(telegram): updateShortMessage fix 'FromID' field

[shadowspore]

#288

[codecov]

Codecov Report

Merging #289 (7aba8ba) into main (cd609a3) will decrease coverage by 0.11%.
The diff coverage is 37.50%.

❗ Current head 7aba8ba differs from pull request most recent head 2864b07. Consider uploading reports for the commit 2864b07 to get more accurate results

@@            Coverage Diff             @@
##             main     #289      +/-   ##
==========================================
- Coverage   70.33%   70.22%   -0.12%     
==========================================
  Files         283      283              
  Lines        8759     8773      +14     
==========================================
  Hits         6161     6161              
- Misses       2008     2016       +8     
- Partials      590      596       +6     

Impacted Files	Coverage Δ
telegram/client.go	73.20% <ø> (ø)
telegram/self.go	46.66% <25.00%> (-24.77%)	⬇️
telegram/handle_updates.go	79.80% <50.00%> (-2.85%)	⬇️
internal/mtproto/rpc.go	40.54% <0.00%> (-24.33%)	⬇️
internal/rpc/options.go	90.00% <0.00%> (-10.00%)	⬇️
transport/server.go	68.08% <0.00%> (-4.26%)	⬇️
internal/rpc/engine.go	71.31% <0.00%> (-4.10%)	⬇️
internal/mtproto/read.go	48.38% <0.00%> (-2.16%)	⬇️
telegram/internal/manager/conn.go	86.48% <0.00%> (+2.70%)	⬆️
internal/pool/pool.go	68.61% <0.00%> (+9.48%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cd609a3...2864b07. Read the comment docs.

[tie]

I don’t think that would work since getSelfID doesn’t invalidate cached ID on re-login as different user. Perhaps we can leave FromID optional in case of Out message and handle that somewhere at a higher level?

[shadowspore]

I don’t think that would work since getSelfID doesn’t invalidate cached ID on re-login as different user. Perhaps we can leave FromID optional in case of Out message and handle that somewhere at a higher level?

Agreed