The test should compare the initialized class with another instance where the setter has been called with the same attribute after initialization, and verify that the instances are not equivalent?
The test should compare the initialized class with another instance where the setter has been called with the same attribute after initialization, and verify that the instances are not equivalent?
Also, possible the name of the test? Reading the test name litterally I would expect the write-only field to not be written🫣
Also, possible the name of the test? Reading the test name litterally I would expect the write-only field to not be written🫣
Maybe the time has come to remove git aliases for common typos🙈
Maybe the time has come to remove git aliases for common typos🙈
I don't control everything end to end, but have the opportunity to work end to end, and team up with experts in subdomains.
I don't control everything end to end, but have the opportunity to work end to end, and team up with experts in subdomains.
In theory, can the data records be anything, like sensor data, allowing atproto to support apps wildly different from Bluesky?
In theory, can the data records be anything, like sensor data, allowing atproto to support apps wildly different from Bluesky?