919059 - Reorganize node APIs

Status: RESOLVED INCOMPLETE

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

Description

[Jordan Santell [:jsantell] [@jsantell]]

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.

Comment 1

[Dave Townsend [:mossop]]

Was there a conclusion from the discussion here?

Comment 2

[Jordan Santell [:jsantell] [@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

Comment 3

[Dave Townsend [:mossop]]

Can you add this to the agenda for the next meeting please?

Comment 4

[Jordan Santell [:jsantell] [@jsantell]]

Added to meeting notes
https://wiki.mozilla.org/Jetpack/Weekly_Meeting/2013-10-22#Agenda

Comment 5

[Jordan Santell [:jsantell] [@jsantell]]

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

Comment 6

[Jordan Santell [:jsantell] [@jsantell]]

Also, in addition to path and fs, move `buffer`, `stream`, and investigate overlaps in `OS` and `net` in our current modules

Comment 7

[BMO Automation]

Add-on SDK is no longer supported so resolving bugs as INCOMPLETE