-
Notifications
You must be signed in to change notification settings - Fork 73
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
Add document storage #163
Add document storage #163
Conversation
|
@mustanggb Thanks for your work. Can you check if removing doctrine/orm 3 support does get yout tests green? |
The tests failures I was fixing were unrelated to orm 3. |
Thanks for the PR! I have dropped the support for ORM 3 as that was clearly a mistake and now the tests pass again. I think we have some psalm errors on master, but could you check if you are introducing any new errors here @mustanggb ? @Chris53897 Would you care to review also? I don't have a lot of experience with MongoDB so it is a bit over my head, but looks good as far as I can tell.. |
Compared to master https://github.com/TheBigBrainsCompany/TbbcMoneyBundle/actions/runs/8031910224/job/21940733804 there are 7 more psalm errors. But i suggest to merge this at it is, and solve psalm errors later. Some of them needs some work and are not so easy. There are just 2 minor things that i noticed. CI testun is changed to 6.4 as 6.0 before. I am not sure why this is not hardcodet to |
@mustanggb Can you please rebase? |
All the previous PRs have been merged allowing for this to be merged to master (will be included in the next major version). Can you resolve the conflicts here @mustanggb and then we can merge this to master. |
The willingness to accept this new feature is very nice to see. Regarding psalm errors, previously 7 were being introduced, I've resolved the 2 unique ones, the remaining 5 are the same as the existing doctrine one's, which I think would be better addressed together as a follow-up. Regarding the bump from Symfony 6.0 to 6.4 for tests this was due to dependency conflicts, I didn't look into it too deeply as they were resolved by switching to 6.4, which I assume would be planned to do at some point anyway. Regarding tests in general, currently (in master) something a bit strange is going on. The But not anymore, to add support for document, then pair history needs to become "storage aware", which means doctrine schema mappings are no longer injected merely by enabling pair history. This means I've added two new test environments:
All other tests run under the usual environment:
So to answer the query, why not hardcode to I guess you could extend Pull request has been rebased, conflict resolved, changes backported, and squashed. |
Thanks a lot @mustanggb - will merge this :) |
MongoDB support