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

Agree on canonical frontend code #4

Closed
spatiebot opened this issue Sep 16, 2019 · 9 comments
Closed

Agree on canonical frontend code #4

spatiebot opened this issue Sep 16, 2019 · 9 comments
Assignees

Comments

@spatiebot
Copy link
Contributor

@congratulatio and @spatiebot in an unrelated thread:

we should appoint one frontend repository as the canonical frontend. We could take the one from airmash-refugees, but, @wight-airmash, you may have a better one somewhere lying around?

airmash.online is currently using the frontend code at congratulation/ao-frontend.
I could integrate the changes from airmash-refugees/airmash-frontend to make it easier to hack on if that helps?

@congratulatio, please feel free to merge the repositories and anoint one of them as canonical. If I can help, I'll be glad to do so.

@spatiebot
Copy link
Contributor Author

@congratulatio <--

@congratulatio
Copy link
Member

Thanks Spatie, I will have a look at it this weekend. Looks they haven't diverged much except on increased readability? So hoping it will be a straightforward task - will let you know if I need any help figuring it out!

@congratulatio
Copy link
Member

I've pushed the changes I made to make this functionally identical to congratulation/ao-frontend.

https://test.airmash.online is now running the latest commit of airmash-refugees/airmash-frontend. Would you mind looking over my changes and reviewing the test site to check I haven't broken anything?

@congratulatio congratulatio self-assigned this Sep 27, 2019
@spatiebot
Copy link
Contributor Author

I looked at the changes, they look good at first glance. The fetch API is the most risky change, I think, but if it improves the code, it's good.

The test site doesn't work on my linux/firefox installation:
Particles.setup is not a function

It does work on my Windows/Firefox setup. Also the regular airmash.online does work on the Linux/Firefox combination.

@spatiebot
Copy link
Contributor Author

It may have been my adblocker. Disabling it and it works. I'm closing this issue.

@congratulatio
Copy link
Member

I think the Fetch API change is okay, it's been on the current airmash.online frontend since congratulatio/ao-frontend@ef54a3c, and from monitoring the /clienterror endpoint I haven't seen anything reported that seems to relate to it.

Could you share more details on your adblocker and the rule that was activated? Maybe one or more of the JavaScript files will need to be renamed to avoid this. Or perhaps could bundle and minify it all for deployment like the original site.

@congratulatio
Copy link
Member

Could you share more details on your adblocker and the rule that was activated? Maybe one or more of the JavaScript files will need to be renamed to avoid this. Or perhaps could bundle and minify it all for deployment like the original site.

@spatiebot in case you didn't see this comment as the issue is closed

@spatiebot
Copy link
Contributor Author

I'll try later.

@congratulatio
Copy link
Member

This is done, now only the frontend code in this repo is served from airmash.online.

https://test.airmash.online is automatically deployed from the latest commit of master branch.

https://airmash.online is deployed manually from tag airmash.online-current (link).

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