-
Notifications
You must be signed in to change notification settings - Fork 7
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
Additional tests and fixes #35
base: develop
Are you sure you want to change the base?
Additional tests and fixes #35
Conversation
…ngs.delete_projects - tests for deleting project with setting enabled and disabled
…we skip onto the next entity rather than stopping.
…ils into its own module for easy testing.
added support for LauncherAction #36 |
(cherry picked from commit b1da619020ec2b4d5ed1b2d6b36d4303bae052c4)
Would it be possible to change the arrow-icon to the Kitsu icon for the "Show in Kitsu" button? |
Hello, could you update the changes? Could you also split the PR into more PRs? There is too much changes for review (smaller PRs -> faster review). |
Thanks for taking a look. I can give it a go breaking it down into different PRs. on the server side there is a mix between using EntityModels and api calls in the current code. This PR replaces any api with Entity in order to make it consistent. From above:
For example: |
The issue is that different changes should be reviewed by different people, that's why I asked for split. It is hard to tell which change is related to what. There are some small bugfixes and big feature changes next to it (multiple features). The features usually needs discussion or may not be merged because of different opinion, but the bugfixes can be merged right away. |
Fair enough, I get that. Would it be possible to get feedback on the replacement of API for Entities please? If that is given the thumbs up or down I will know how to proceed with the PRs. |
Note that it is hard to tell, because for example I don't know which exact changes are related to it. |
First of all thank you @scottmcdonnell for your contribution! To push it through, we really need to split this massive PR to smaller pieces as it is not approvable in the current state. each bulleted item in your description should be a separate PR honestly. |
No problem, I will break into smaller PRs. I am on a few big projects at the moment but will come back to this as soon as I can. |
Would be great to get some 🔥 progress into this one. |
Sorry was very snowed under. PRs started. Can I make PRs dependant on each other? The testing requires fixtures and set up that is common to each PR and some changes have larger dependencies. |
Hello, |
I had a few issues with the 1.1.0 sync.
calculate_end_frame
to failLastly some of new bits were using the Ayon api via httpx to save users/projects etc but this is mixed with the existing
server/kitsu/utils.py
which uses Postgres for gets and Entity models to save and update. This I found really confusing, it should be all one or the other. It didn't make much sense to me for Ayon (in an ayon api endpoint) to be calling itself through the api when the models are available and the postgres connection is already initialised, it seems an unnecessary overhead, so I converted the api calls to model calls in utils.py to make it consistent.I saw afterwards that this was discussed on discord a bit, and the preference was API, but I think it should be consistent throughout utils.py - so not sure what the team thinks on this one!