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.

Sign up for GitHub

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

Jump to bottom

Renaming services to better reflect their purpose #22

Open
amitkparekh opened this issue Feb 6, 2021 · 0 comments
Open

Renaming services to better reflect their purpose #22

amitkparekh opened this issue Feb 6, 2021 · 0 comments
Labels
code quality Ensuring the codebase doesn't turn into mush documentation Improvements or additions to documentation good first issue Issues that don't require previous experience with Ayesaac

Comments

@amitkparekh
Copy link
Member

I feel like web should become api, as it's literally an API that allows the website and other external sources to interface with the application.

ExternalInterface could be renamed to something simpler since all it does is export the data so it can then be downloaded by the frontend to return the information.

I welcome any ideas about this!
@amitkparekh amitkparekh added documentation Improvements or additions to documentation good first issue Issues that don't require previous experience with Ayesaac question Further information is requested code quality Ensuring the codebase doesn't turn into mush and removed question Further information is requested labels Feb 6, 2021
@amitkparekh amitkparekh mentioned this issue Feb 6, 2021
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
code quality Ensuring the codebase doesn't turn into mush documentation Improvements or additions to documentation good first issue Issues that don't require previous experience with Ayesaac
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amitkparekh