• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle



  • Aside from device ID, or maybe if you’re using a billing address as something from Australia, I can’t see how they would be, you’ve stated location services are off, VPN will mask the ip.

    I didn’t even need to use a VPN in my cases between Canada and the US, changing to an account that was in the region that allowed the purchase was all I had to do.

    That being said if I changed my Canada account to use the billing address of my US residence instead of my Canadian residence when on the Canadian region, I would get region locked I found, so if you have a primary payment method on file using your AU address you could try temporarily removing or modifying it to have a different address



  • I mean they are currently /ok/ but since it’s only samsung devices it bounces off instead of every android device it doesn’t have the versatility that the Apple airtags have (where it bounces off any apple device and any android device with the app), so if it’s between one of the other I would go with air tag since you can still use them on android (with a secondary app) but as always YMMV since it’s made for Apple devices

    that being said, might be changing with googles support for trackers!



  • Yeah I fully agree typescript does help in terms of knowing what type of types you should be supplying to functions, and for the most part I do use it for non-library purpose/anything that doesn’t rely on a third party, I just feel like typescript isn’t worth it when you have data that’s returned at run time that’s controlled by a third party service. You end up coding more in class definition files then you would just using normal tests


  • So the biggest issue is the project relies extremely heavily on a third party API service, and since the data is received over said service, typescript is unable to infer what the objects the API is sending is because it sends during runtime, to get around this I have to define everything that I expect that the library is going to have to handle that would be Recieved, since any object that the API is going to return is just going to have a type of any if it’s not defined, this on top of the fact that the API has stated that the data being sent should not be relied on for being accurate and types may change randomly(usually it does not but it has happend, it sucks but out of my control) means that I generally also have to have a function level test the data when it’s received to make sure that the value is being supplied are the correct type and are formatted in a way that the library can still understand it. Which means that it’s able to catch any inconsistency of typing before it would be processed anyway, and would either warn or throw depending on how important the function is to actual operation.

    The reason why I would call it standard is because it seems like basically anywhere you look if you are using node, you’re using typescript they go hand in hand it seems as of the last two or three years, but honestly I’ve never really understood the benefit of, I’ve always thought it was a fairly standard to have at the beginning of a function the documentation of what each perimeter should be unless it is easily verified by looking at it.

    As for my setup, it’s not very advanced it’s just Sublime Text with linter hooked to it, which does tell me on save if there’s a typescript error or if I formatted something wrong, but again even if one did happen to slip through that it would fail during the testing phase due to the fact that it would throw at the function level.

    My opinion of my experience with typescript has been that it’s great if everything is operated in house, but the second you start having to deal with stuff that comes from an external source any advantage of the check just seems not worth the extra effort to make sure typescript works right.


  • I mean I guess that could be helpful, I’ve never really had that issue so I have yet to see the benefit of it. I just find it useless work that you’re typing out for something that the engine itself isn’t going to be able to see anyway, which means you’re going to have to have unit tests coded in regardless. And I wouldn’t say just a little more coding, typescript when implemented into my project doubled the amount of code provided, I’m trying to use it because I do understand it’s a standard, but I really don’t understand why it’s a universal standard, considering that everything it does is completely syntax sugar/coder side and it doesn’t actually interact with the underlying engine. I feel the same way about coffee script honestly.


  • I’m in this post and I don’t like it.

    That being said I try to have specific types in my typescript but coming from working without typescript, there’s so much more words involved using typescript and for what I use it for I don’t really see the use case. Sure it helps you realize what part of the script needs what data types but it adds so much more complexity in the code that I’m not really sure it’s worth in the first place.