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
Hi @dwinston, I'm sending this as a GitHub Discussion with the following quote in mind (from the office hours invite):
(2) updating our situational awareness to support subsequent office-hour Q&A and infra-sync agenda items. We will prefer to limit in-Slack responses -- even to 1:1 direct messages (DMs) or to personal @-mentions -- to briefly-qualified links to public GitHub issues
I took that to mean you generally prefer Q&A stuff like this happen on GitHub as opposed to Slack.
I have a question about this code snippet in the validate_json function (in nmdc_runtime/util.py):
I see there are a couple reference to @type in tests/test_api/test_endpoints.py, where the author seems to me to want to ensure that the validate_json function handles it a certain way:
questionFurther information is requestedX SMALLLess than 1 day
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi @dwinston, I'm sending this as a GitHub Discussion with the following quote in mind (from the office hours invite):
I took that to mean you generally prefer Q&A stuff like this happen on GitHub as opposed to Slack.
I have a question about this code snippet in the
validate_json
function (innmdc_runtime/util.py
):What is
@type
?I see there are a couple reference to
@type
intests/test_api/test_endpoints.py
, where the author seems to me to want to ensure that thevalidate_json
function handles it a certain way:Beta Was this translation helpful? Give feedback.
All reactions