Skip to content
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

[ENH] annotation key #212

Merged
merged 7 commits into from
Feb 22, 2022
Merged

[ENH] annotation key #212

merged 7 commits into from
Feb 22, 2022

Conversation

jdkent
Copy link
Member

@jdkent jdkent commented Feb 16, 2022

references #210

relevant changes

  • add note_keys parameter to annotations endpoint
  • make it so you cannot push notes with different column names than specified in note_keys
  • scenarios
    • creating annotation but have not created any columns yet
      • this is okay
    • adding notes to annotation without first//concurrently filling out note_keys
      • raises error
    • adding columns to note_keys but have not created any notes
      • this is okay
    • adding/removing/changing type existing note_keys and not simultaneously changing notes
      • raises error
    • adding/removing/changing note columns without simultaneously changing note_keys
      • raises error

@adelavega @nicoalee: here is the current behavior of this pull request, let me know if this looks reasonable or if y'all would want changes in how this pull request behaves to different scenarios.

@nicoalee
Copy link
Collaborator

references #210

relevant changes

  • add note_keys parameter to annotations endpoint

  • make it so you cannot push notes with different column names than specified in note_keys

  • scenarios

    • creating annotation but have not created any columns yet

      • this is okay
    • adding notes to annotation without first//concurrently filling out note_keys

      • raises error
    • adding columns to note_keys but have not created any notes

      • this is okay
    • adding/removing/changing type existing note_keys and not simultaneously changing notes

      • raises error
    • adding/removing/changing note columns without simultaneously changing note_keys

      • raises error

@adelavega @nicoalee: here is the current behavior of this pull request, let me know if this looks reasonable or if y'all would want changes in how this pull request behaves to different scenarios.

this logic looks good and intuitively makes sense to me

@adelavega
Copy link
Member

adelavega commented Feb 17, 2022

LGTM!

My only minor concern is that using python logic prior to sql inserts could potentially slow things down, but unless we a see a specific problem w/ performance I don't think we need to worry about it too much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants