Closed Bug 919059 Opened 11 years ago Closed 6 years ago

Reorganize node APIs

Categories

(Add-on SDK Graveyard :: General, defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jsantell, Unassigned)

References

Details

Currently, the `fs` module based on node lives under the `io` directory and the `path` module lives under the `fs` directory, which both make sense independently, but together this is weird. We should discuss if our node-parity modules should be in a unique place or organized relevant to the SDK. In this scenario, perhaps making `fs` a high level API (after more refinement), with `fs/path` making sense then.
Was there a conclusion from the discussion here?
Flags: needinfo?(jsantell)
No -- something we should probably bring up next meeting, as well as organizing of future modules, if it will influence our 'node' modules at all
Flags: needinfo?(jsantell)
Can you add this to the agenda for the next meeting please?
Flags: needinfo?(jsantell)
Flags: needinfo?(jsantell)
Priority: -- → P3
As per today's discussion, we agreed on moving node APIs (io/fs, fs/path) to a directory `node`, as sibling to `sdk` and `toolkit`. We will leave modules with deprecation warnings in their previous place. https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-11-05#Agenda
Summary: Reorganize `io/fs` and `fs/path` → Reorganize node APIs
Blocks: nodemodules
No longer blocks: nodeification
Also, in addition to path and fs, move `buffer`, `stream`, and investigate overlaps in `OS` and `net` in our current modules
Add-on SDK is no longer supported so resolving bugs as INCOMPLETE
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.