Closed vsfeedback closed 6 days ago
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.
See our Issue Management Policies for more information.
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work] Hello I need a list of data whose primary key is long so that I can search them faster. When I created this list, I couldn't find some key values, but I was sure that the key used was correct because I had tested it many times. After a lot of research, I noticed a terrible bug on the Blazer side, and I have put it in the image below.
It should be noted that the problem is not only in the display of the data, but the problem is certainly in the infrastructure of the data types, because when this value was passed to other classes, the data was saved on the client side and then read again, the incorrect information was stored in memory. I had to change the data type of my cache key to a string of numbers Please check, I am in complete shock
Original Comments
Feedback Bot on 4/27/2024, 06:17 PM:
(private comment, text removed)
Original Solutions
(no solutions)