You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A big one is that I think protocol enforcement needs to be done via classes / helpers somehow, but at the same time I don't think it should be 100% necessary. (Heck it isn't even in streams3)
A more formal specification than just the reference would be useful, in the same way it would be useful to have (or had) that kind of thing for streams3.
This should also allow the project at a spec and then "core classes" level to be moved into the node org without having to drag every sub module in.
The text was updated successfully, but these errors were encountered:
So I've been realizing a couple related things...
A big one is that I think protocol enforcement needs to be done via classes / helpers somehow, but at the same time I don't think it should be 100% necessary. (Heck it isn't even in streams3)
A more formal specification than just the reference would be useful, in the same way it would be useful to have (or had) that kind of thing for streams3.
This should also allow the project at a spec and then "core classes" level to be moved into the node org without having to drag every sub module in.
The text was updated successfully, but these errors were encountered: