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

[Feature Request] AFat Integration #103

Open
spenjer1 opened this issue May 9, 2023 · 1 comment
Open

[Feature Request] AFat Integration #103

spenjer1 opened this issue May 9, 2023 · 1 comment

Comments

@spenjer1
Copy link

spenjer1 commented May 9, 2023

Context

Add the creation of ESI FATLinks through allianceauth-afat module when creating a ping.

Describe the feature you have in mind

Add a checkbox or button (similar to SRP checkbox) to allow auto-creation of ESI Fatlinks from a formatted ping.
Fleet Name & Fleet Type are already populated within both modules.
Obviously the FC Name would need to be activated from the ESI Character Select screen.
When the check box for ESI FATLink is checked, after a user has clicked "Create Ping", open a new browser tab of the ESI Character Select page.
The character selected on that screen would dictate the FC the FATLink is under (not the FC name in Fleet Pings).

Since each FATLink uses a unique Callback key, the callback would need to be processed locally within the Fleet Pings module, unless there was some way to to have AFAT do the processing of the callback creation?
https://[URL].com/fleet-tracker/fatlink/create/esi-fatlink/callback/[CALLBACKKEY]/

Thanks in advance for looking into this feature request!

@ppfeufer
Copy link
Owner

Interesting idea, but not implemented that easily, since there is no way to make sure that:
a) The FC already has a fleet open, which is mandatory for ESI FAT-Links to work
b) The one creating the ping is the actual FC

But I keep this one open, in case I find a solution.

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

No branches or pull requests

2 participants