-
Notifications
You must be signed in to change notification settings - Fork 20
Issues: samvera/valkyrie
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Valkyrie::StorageAdapter documentation correction?
documentation
question
#951
by dchandekstark
was closed Apr 25, 2024
Blank values for type Valkyrie::ID cause URI-to-ID lookups to return the Fedora base path as an ID
#944
by randalldfloyd
was closed Feb 1, 2024
Postgres query service should use find_each in #find_all and #find_all_of_model for efficiency
#924
by dchandekstark
was closed Mar 23, 2023
Update the gemspec to require MFA for RubyGems releases
#898
by jrgriffiniii
was closed Jun 17, 2022
Valkyrie StorageAdapter Files shouldn't open a file handle on instantiation
#869
by tpendragon
was closed Oct 18, 2021
Valkyrie StorageAdapter Files should have a
#close
method
#868
by tpendragon
was closed Oct 18, 2021
Update references of hard-coded legacy master branch name to main branch name
#861
by kelynch
was closed Jun 30, 2021
Shared specs for lock token messages should be less stringent.
#849
by tpendragon
was closed Oct 18, 2021
Add supported ruby versions to development documentation
documentation
#846
by tpendragon
was closed Oct 19, 2022
Condense and improve developer spin-up documentation & process
Tooling
#838
by tpendragon
was closed Oct 20, 2020
Persisters should error if asked to save a persisted resource which doesn't already exist.
enhancement
#837
by tpendragon
was closed Oct 15, 2021
Document recommended resource modeling practices
documentation
#836
by tpendragon
was closed Jun 26, 2020
Problem with optimistic locking wiki page "Example functionality" section.
documentation
#824
by coblej
was closed Feb 10, 2020
Change set shared spec assumes resource does not have optimistic locking enabled
bug
#822
by coblej
was closed Feb 10, 2020
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.