planetazuzu/codigo0
1
0
Fork 0
Code Issues Pull requests Actions 1 Packages Projects Releases Wiki Activity
codigo0/node_modules/readable-stream/doc/wg-meetings/2015-01-30.md
planetazuzu 5d7a6500fe refactor: Fase 1 - Clean Architecture, refactorización modular y eliminación de duplicidades 
- ✅ Ticket 1.1: Estructura Clean Architecture en backend
- ✅ Ticket 1.2: Schemas Zod compartidos
- ✅ Ticket 1.3: Refactorización drugs.ts (1362 → 8 archivos modulares)
- ✅ Ticket 1.4: Refactorización procedures.ts (3583 → 6 archivos modulares)
- ✅ Ticket 1.5: Eliminación de duplicidades (~50 líneas)

Cambios principales:
- Creada estructura Clean Architecture en backend/src/
- Schemas Zod compartidos en backend/src/shared/schemas/
- Refactorización modular de drugs y procedures
- Utilidades genéricas en src/utils/ (filter, validation)
- Eliminados scripts obsoletos y documentación antigua
- Corregidos errores: QueryClient, import test-error-handling
- Build verificado y funcionando correctamente
2026-01-25 21:09:47 +01:00

2.2 KiB
Raw Blame History

streams WG Meeting 2015-01-30

Links

Agenda

Extracted from https://github.com/iojs/readable-stream/labels/wg-agenda prior to meeting.

  • adopt a charter #105
  • release and versioning strategy #101
  • simpler stream creation #102
  • proposal: deprecate implicit flowing of streams #99

Minutes

adopt a charter

  • group: +1's all around

What versioning scheme should be adopted?

  • group: +1’s 3.0.0
  • domenic+group: pulling in patches from other sources where appropriate
  • mikeal: version independently, suggesting versions for io.js
  • mikeal+domenic: work with TC to notify in advance of changes simpler stream creation

streamline creation of streams

  • sam: streamline creation of streams

  • domenic: nice simple solution posted but, we lose the opportunity to change the model may not be backwards incompatible (double check keys)

    action item: domenic will check

remove implicit flowing of streams on(‘data’)

  • add isFlowing / isPaused
  • mikeal: worrying that we’re documenting polyfill methods – confuses users
  • domenic: more reflective API is probably good, with warning labels for users
  • new section for mad scientists (reflective stream access)
  • calvin: name the “third state”
  • mikeal: maybe borrow the name from whatwg?
  • domenic: we’re missing the “third state”
  • consensus: kind of difficult to name the third state
  • mikeal: figure out differences in states / compat
  • mathias: always flow on data – eliminates third state
    • explore what it breaks

action items:

  • ask isaac for ability to list packages by what public io.js APIs they use (esp. Stream)
  • ask rod/build for infrastructure
  • chris: explore the “flow on data” approach
  • add isPaused/isFlowing
  • add new docs section
  • move isPaused to that section