-
Notifications
You must be signed in to change notification settings - Fork 33
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
OEP-32 has been superseded and should be updated #407
Comments
Do you think the guidance is still correct for ids internal to the platform, and this is just about correcting guidance for external ids? |
The ADR only covers the case of external IDs. So, job one would be correcting that. My preference would be that auto increment database IDs were not used as identifiers, but that's a much bigger, breaking, change I believe. |
I agree with your preference, but the point of the OEP was to codify what to use, given the reality of our situation. Better than using user id in some cases, and username in other cases, as was happening. |
It is partially correct. It is valid for internal ids, and invalid for external ids. I'm not sure if there are legacy exceptions to the external ids case that do use this same internal id. |
Thanks. Assuming #586 passes, I will mark this OEP as Needs Revision and point to this thread. |
Put OEP-32 in Needs Revision status, please take a look at #603 - this ticket will be kept open for discussion on how to actually update the OEP for real |
Partially addresses openedx#407
The guidance for external ids in OEP-32 is currently incorrect and that OEP has been superseded by this ADR.
The OEP needs a significant rework.
The text was updated successfully, but these errors were encountered: