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
Currently Bluejay is all one file - we should split it, to the degree it makes sense, by class and/or what is appropriate to get the files to roughly 50-250 lines each.
The text was updated successfully, but these errors were encountered:
@apike, @nbrooke the source is now broken up into different logical files. Totally open to suggestion and changes.
A few notes on some of the reasonings behind renaming certain things:
Generic class names like “Sendable” and “Receivable” are all prefixed with “Bluejay” to make codebases that use Bluejay clearer. Otherwise if there are other libraries or context that share similar terminologies, the code can be a bit confusing to understand and slower to read.
Other generic class names such as “ServiceIdentifier” or “DataPadding” are not prefixed with “Bluejay” because they are a bit more specific already, and by trading off a bit of consistency in naming we can prevent absurdly long names in a few cases.
Currently Bluejay is all one file - we should split it, to the degree it makes sense, by class and/or what is appropriate to get the files to roughly 50-250 lines each.
The text was updated successfully, but these errors were encountered: