Open Merge Requests
===
IDComponentReporter Assignee Updated For Version
PrioritySummary
--- - --
- --
BIT-1211
[
https://bro-tracker.atlassian.net/browse/BIT-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robin Sommer updated BIT-1209:
--
Resolution: Merged (was: Fixed)
Status: Closed (was: Merge Request)
bro-cut needs tests
It seems like one area where our documentation is sorely lacking is the
weirds. Apart from comments in the code, I believe the only documentation
is the name of the weird itself.
Is there a mechanism in Broxygen to document weirds? If not, has anyone
thought about what such a mechanism might look
On Jun 27, 2014, at 3:35 PM, Vlad Grigorescu v...@grigorescu.org wrote:
Is there a mechanism in Broxygen to document weirds? If not, has anyone
thought about what such a mechanism might look like?
There’s not currently a mechanism. Things that Broxygen can easily aid in
documenting are
On Fri, Jun 27, 2014 at 21:41 +, you wrote:
A suggestion would be to change weirds to use an enum instead of a
string value.
Yeah, either that, or introducing a structured ID namespace (e.g.,
http.client.unexpected_data), potentially with some static analysis
to find IDs that aren't
