Remove Identifiable
See original GitHub issueIdentifiable
really doesn’t naturally fit into the API anymore as its move to Optional
has made obvious that the optionality really gets in the way of link creation etc. Also, with the rename of ResourceSupport
to RepresentationModel
, the idea of a model being identifiable feels rather weird as well.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
New options for removing your personally identifiable ...
For many years, people have been able to request the removal of certain sensitive, personally identifiable information from Search — for ...
Read more >Remove select personally identifiable info or doxxing content ...
You can request to remove personally identifiable information (PII) from Google Search results. This information includes: Confidential government ...
Read more >Data publication: Removing identifiers from data
If you have to collect identifiable data, then try to employ data collection practices that will make removing identifying information ...
Read more >Google Search Allows Removal Of Personally Identifiable ...
Google is rolling out new ways to remove personally identifiable information from search results such as phone numbers and physical ...
Read more >Request to Remove or Replace Personally Identifiable ...
Home; Remove or Replace PII. Request to Remove or Replace Personally Identifiable Information. As part of the registration process, the U.S. Copyright ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Removing this has caused me a fair bit of pain. Other than this GitHub issue it isn’t documented (that I could find) and isn’t mentioned at all in the migration guide. The removal of the slash(Identifiable<?> identifiable) method from LinkBuilder caused my code to fall back to the slash(Object object) method which then produced bad links without throwing any errors. Luckily my tests saved the day. Might be worth adding it to the migration guide to save others the trouble of having to figure this out for themselves.
1 year after @beardy247’s comment and still no mention of this breaking change anywhere except this GitHub issue. Would really appreciate some form of documentation on migrating a code base making use of
Identifiable
in cases where the migration script does not work.