-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
[REF] 8.0 mgmtsystem_action #22
Conversation
@@ -43,6 +43,6 @@ | |||
'board_mgmtsystem_action.xml', | |||
], | |||
"demo": ['demo_action.xml'], | |||
'installable': False, | |||
'installable': True, | |||
} | |||
# vim:expandtab:smartindent:tabstop=4:softtabstop=4:shiftwidth=4: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, but it would be nice if you removed the vim lines.
ea2e765
to
67f1498
Compare
<field name="res_model">mgmtsystem.action</field> | ||
<field name="view_type">form</field> | ||
<field name="view_mode">tree</field> | ||
<field name="view_id" ref="view_mgmtsystem_action_tree"/> | ||
<field name="domain">[('state', 'in', ('draft','open','pending'))]</field> | ||
<!-- TODO check that names match what's present --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a work in progress?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, but was looking for some pointers.
Can someone have a look why travis crashes? |
Restarted it and it doesn't solve the issue. |
Yeah, I'm experimenting same issue on l10n-spain branch, so it's related to odoo core. For now, I haven't investigated any solution. |
Good news. Seems to work now |
The state/stage stuff doesn't bother me a lot, since I believe that should be revisited at a later moment. So IMO the commented stuff on it can perfectly be left in the code for now. |
Coverage has gone down -7.69%, please add tests for mgmtsystem_action/mgmtsystem_action.py
|
Come on @bwrsandman: it's not like it's a new module. It's just a port from v7. |
This is a strong recommendation, I won't block it, but I won't approve it without tests. @dreispt I have worked on porting the mgmsystem modules to v7 when I started and I know how much the code needs be better. Tests are the most beneficial when porting to a new version since behaviour is much more likely to do unintended things. A drop in coverage (esp. from 100%) should be objected. |
I see, you're asking it but not demanding - that's OK. From my PoV I would like to see the just "working" in v8 ASAP so that we have the base to improve it. Much of the current code is related to state/stage management, and that will probably be retired. |
It is used and only contains things from mgmtsystem_nonconformity
Should I remove the workflow file, it doesn't seem to be required anymore? I'm not sure it is still relevant.
|
When doing `case.user_id = None`, it will throw this error: IntegrityError: null value in column "partner_id" violates not-null constraint
👏 |
Excellent coverage! You can remove openupgrade analysis file and migration scripts, because they are for v7. You should build another ones for v8 if there are changes in DB layout. |
👍 As for the transition, I still think it's in use. What makes you think it should be removed? |
Workflow is not relevant if people involved in the action are added as followers and receive notifications of state changes. |
@bwrsandman, are you asking me? I ask about removing migration files because it's for v6 to v7 migration, not for v7 to v8. |
@pedrobaeza Sorry for the confusion: I am asking @llacroix
|
@bwrsandman The workflow transition was calling The other workflow for |
@pedrobaeza how about updating from 6 to 8 ? Is it possible or the "safe" way would be to update from 6 to 7 and from 7 to 8. Right now, there is no migration from 7 to 8 the model didn't change as far as I can tell. |
@llacroix good point, that should be moved to NC, then,
The url will get changed depending on your deployment. Try changing your port, you'll see it changes.
You can only do an upgrade from one version to the next: Maybe in the future OpenUpgrade could support such a high jump but it is not the case today. That being said, I don't really mind if the old migrations stay, they serve as examples for future migration scripts and they shouldn't cause any problems for people in v8 |
OK, we have those scripts on v7 branch, but if you want to keep it, it's not a blocking issue. |
Is there anything else to do so we can pass to other modules? Many modules can't be merged because they depend on this one. |
@llacroix To merge this ASAP. |
👍 No huge issue (in fact it looks amazing), but I would wait for @max3903 to approve |
👍 |
[REF] 8.0 mgmtsystem_action
[ADD] document_url: Module to attach URLs as documents
BSCOS-100 Language and tags on company's contacts form
The current module inherit
crm.claim
while thestate
attribute doesn't exist anymore. I made some changes to use thestage_id
instead but I'm not so sure it's a good idea. I'm open to suggestions.