-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSR documentation clarification #960
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just wondering about the updated hyperlink.
package-lock.json
Outdated
"resolved": "https://registry.npmjs.org/util/-/util-0.10.3.tgz", | ||
"resolved": "http://registry.npmjs.org/util/-/util-0.10.3.tgz", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this correct? I'd expect all addresses to be http**S**
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hum that's a good point. This is automatically generated but Ill ping the libsbp
channel to see if we can update the generator
package-lock.json
Outdated
"resolved": "https://registry.npmjs.org/util/-/util-0.10.3.tgz", | ||
"resolved": "http://registry.npmjs.org/util/-/util-0.10.3.tgz", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same as above.
a36db29
to
fefae2c
Compare
* Specification update * Automatic generation
Clarifying the code biases signal encoding and correcting a few nits