Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to show the ideal tag for a tag service, not the user's preferences, in the client API #1598

Open
roachcord3 opened this issue Sep 21, 2024 · 0 comments

Comments

@roachcord3
Copy link
Contributor

roachcord3 commented Sep 21, 2024

I would like an optional parameter on /add_tags/get_siblings_and_parents that would have the ideal_tag field show the ideal tag on the tag service under which it's keyed.

e.g. if a user has thigh-highs as their ideal tag for thighhighs in my files (which they set as higher precedence), but the PTR has thighhighs as the ideal tag, this option would make thighhighs be returned as the ideal_tag for the PTR's service key, but thigh-highs would still be the ideal_tag for the my files service key. Right now, per your docs (see screenshot below), it displays according to the user's preferences only.

Also, the siblings and parents here are not just what is in tags->manage tag siblings/parents, they are the final computed combination of rules as set in tags->manage where tag siblings and parents apply. The data given here is not guaranteed to be useful for editing siblings and parents on a particular service. That data, which is currently pair-based, will appear in a different API request in future.

My use case is that I want to have the program I'm writing, which cleans up pending tags for users before they push them, to respect remote tag services' preferences over user-specific idiosyncrasies. This is "greener" in the sense that most people don't override remote tag repo's siblings, so it means less processing for most clients. Plus, it just seems cleaner and more polite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant