Completing the JWT Authentication PR
This week was relatively light compared to previous weeks, but I focused on resolving the remaining issues related to the ES256 JWT Authentication PR.
While preparing the PR for review, Dr. Shawn noticed that the Dart SDK version in pubspec.lock had been downgraded:
dart: ">=3.11.0 <4.0.0"
→
dart: ">=3.10.3 <4.0.0"
During my testing, some dependency-related changes had unintentionally modified the SDK requirements. Dr. Shawn highlighted that we should avoid unnecessary version regressions unless there is a valid reason.
After reviewing the changes, I corrected the issue and ensured that the project remained on the intended Dart SDK version. Once the fix was completed, I updated the PR and submitted it again for review.
PR Successfully Merged
Following the earlier JWT verification issue involving the iat field, Dr. Shawn successfully implemented the necessary fix on the server side. With both the client-side and server-side changes in place, the JWT Authentication PR was finally approved and merged.
This marked the completion of the migration from HS256 to ES256 authentication for the QR scanner feature.
Lessons Learned
Although this week involved fewer development tasks, it reminded me that software development is not only about implementing features. Paying attention to version changes, dependency management, and code review feedback is equally important.
I also learned the importance of carefully reviewing every file included in a pull request. Small changes, such as an unintended SDK downgrade, can create confusion for other developers and should always be verified before submission.
Looking Ahead
The JWT authentication implementation is now complete, and the server-side issue has been addressed. The next step is to validate the solution in a real-world environment during the upcoming event.
I am looking forward to testing the QR scanner again and hope that the authentication process will work smoothly under actual event conditions. It will be exciting to see the feature functioning successfully after the debugging and migration efforts over the past few weeks.
0 Comments