You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Scorp アプリがバックグラウンド・フォアグラウンド・タスクキル状で取得したプッシュ通知から任意の画面に遷移させるまで。 Proposal Firebase Cloud Messagingの公式 以下は某アプリに落とし込んだケース。 ポイント①は「アプリ終了状態とそれ以外」でプッシュ通知の表示を制御している。 アプリ終了状態の場合は.getInitialMessage()で取得したinitialMessageを引数に、それ以外の場合は.onMessageOpenedApp()で取得したプッシュ通知を引数にポイント②の_handleMessage()を呼び出している。 このケースでは任意の画面に遷移させる且つ任意の画面タイプで表示させる仕様に対応しようとしていて、ポイント②の_handleMessage()ではプッシュ通知のデータの中からis_allというキーの値をみて遷移先の画面タイプを
I’m back to the regular posting schedule. No more game development, at least for now. The topic of always valid domain models is beaten to death already. There’s little doubt in the DDD camp that your domain model should be valid at all times. It’s much easier to program in an environment where you know that objects you operate reside in a valid state and you don’t need to worry about their intern
This post describes some (more) advanced error handling techniques. I’ll probably do a series because this topic is large and there’s quite a few things that need to be cleared out, but we’ll see. This first article in the series is about organizing errors in your application. It’s also an answer to a question I received 3 times from different people during the past couple of weeks. How can I go a
UPDATE 5/13/2021: the course has been published, check it now here: Validation and DDD. I’m working on a new Pluralsight course on the topic of validation and DDD, with the help of the FluentValidation library and .NET data annotations (attributes). So expect a couple of posts about validation in the near future. In the preparation for the course, I was re-reading some old articles about always-va
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く