Remove tag replacement check api
See original GitHub issueTo revert #63.
This pr has no real value and causes problems with custom Tag
implementations, as seen in jellysquid3/lithium-fabric#33
The fact that a tag has been replaced offers no actual insight; we shouldn’t make an assumption on it, especially given that all data packs can be unloaded, i.e. your tag’s default elements may be absent even if the tag isn’t replaced but your mod data pack is just not loaded.
Yes, I blame asie again. #63 in essence is even less relevant to the api compared to #562, and its merge I’d argue was a total fault.
For proper compatibility and removal, fabric should have added removal support such that a tag can remove elements with certain ids/incertain other tags.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to remove a single TAG from a Work Item via API - MSDN
I'm having trouble identifying the method to delete a single, specific TAG from a work item via Rest API. I've been able to...
Read more >REST API for adding and removing tags
Available from 9.2.14. You can add and remove tags for any software component by using REST API.
Read more >Remove a tag from a contact - ActiveCampaign
A DELETE call to /contactTags/22 will delete the association of "John Doe" and the "foo" tag. It will not delete the "foo" tag...
Read more >ADO CLI can't remove tags - Stack Overflow
I can confirm that the az boards work-item update command is no longer removing/replacing tags with the ones that are passed, and this...
Read more >Remove Tags - Palo Alto Networks
Remove tags from your endpoints. ... Document:Cortex XDR™ API Reference ... Description. Remove one or more tags from one or more endpoints.
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 FreeTop 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
Top GitHub Comments
It’s not meant for modded tags, no! It’s specifically meant for the situation in which Fabric API overrides, say, a hardcoded block type if-check in vanilla, as we cannot know if another mod, Fabric or non-Fabric, hasn’t overridden it. The alternatives are:
In the vision of Fabric API as minimally intrusive, and in the codebase I worked in when designing this, the solution was perfectly sensible for me, and I recall seeking input about it from other developers - though my memory is famously terrible, so I might be wrong on that last bit. However, I do think that everything should be questioned (otherwise Fabric wouldn’t exist at all!) and if codebase circumstances changed (by, f.e., Mojang removing most hardcoded checks out into tags themselves, or by the implementation of Tag becoming less conductive to this), this should be rethought.
Remember - snapshots are the time to do breaking changes in Fabric! Don’t worry about snapshot mods and snapshot packs - they will disappear in weeks and perish. Only worry about the stability of release versions.
Inapplicable for 1.18.2+