6 Commits (d857f2013f8ead2f4e8f69a4429c1af15a5d438b)

Author	SHA1	Message	Date
James Bardin	322ef7f10b	make sure write-only nested types are found ... While we skip whole blocks in the code, make sure we don't skip whole nested attributes.	1 year ago
James Bardin	bfbeee9592	wo attrs can be null, but cannot traverse null ... There were two existing tests for incorrect return values, which the code still satisfied. While we can return paths _to_ null values which are write-only, you cannot traverse a null value to a write-only path.	1 year ago
James Bardin	a3e7be3301	remove copyAndExtendPath which has a generic equivalent	1 year ago
James Bardin	70d6319486	additional WriteOnly tests for NestedSingle	1 year ago
James Bardin	a3719fe3ee	WriteOnlyPaths was returning the wrong paths ... WriteOnlyPaths was returning some paths from values which did not exist, while missing others which did. The process is exactly the same as for SensitivePaths, so replace the methods with an exact copy changing out the appropriate field and method names. There's probably a way to abstract these into a single method, but it wasn't apparent if or how that's possible without a much more complex method, so for now I left them as duplicates with comments to check the other when changes are made.	1 year ago
Radek Simko	0188be70e8	fix: Allow WriteOnly attributes to require replacement (#36313) ... * fix: Allow WriteOnly attributes to require replacement * address feedback * add test	1 year ago