Comments (3)
Note: this ticket was advertised in https://discuss.openedx.org/t/guidelines-for-proactive-vs-reactive-event-definitions-in-openedx-events/10661, which may or may not collect its own comments.
from openedx-events.
Back when we had the earliest draft of what eventually became OEP-50 we had a list of possible places in the code where we would want to extend based on common key models of the platform.
You can still find those in the google doc that is linked from oep-50. https://docs.google.com/document/d/1jhnudz6AVtVt0ZSRSwOwj9gJ0lsDDn_8mUCPehLPzLw/edit#heading=h.vo2ywbxdhh5
I think that as long as we are reasonably going to keep them supported for a while the more available events the better. Ideally as an extension or consumer developer I should be able to first look at the list of available events hoping to find that the one I need is already present. Having to include the event in the core first in order to be able to extend it later has two negative consequences IMHO.
- to avoid doing the double work I might be tempted to use a different arquitecture and end up never publishing the event.
- the data passed to the event might be too specific for my current use case. We try to discuss this when the event is being created at this repo, but we might not always catch that.
from openedx-events.
Thanks @felipemontoya. If we were to document your stance and reasoning, we would just need to find a good home for it in the existing docs.
from openedx-events.
Related Issues (20)
- Address debugging improvement suggestions from community feedback
- Improve documentation for events across Open edX releases HOT 1
- How to implement organization-scoped events
- Address documentation improvement suggestions from community feedback
- State of the art repository to exemplify usage
- How to create an event from start to finish
- How Open edX Events work
- How to implement events with long term support
- Templates for creating new events
- Which events are in each named-release
- Where each Open edX Events is being sent
- Cross-repo collection of all events in the ecosystem
- Clarity about which events are event-bus capable and the differences between bus and non-bus events
- How testing is done in event-bus implementations
- Improve how to contribute and review expectations
- Include comprehensive list real life usage
- Get receivers for events in runtime
- Logging improvement for event receivers
- Events around course progress for enrolled learners
- Test openedx-events on Ubuntu 24.04
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openedx-events.