David Chandek-Stark
David Chandek-Stark
**Describe the bug** Non-aliased schema name `:schema` appears to cause relation registration problems. **To Reproduce** My relation has this configuration snippet: ``` schema(:schema) do ... end ``` When I register...
This restores the route ordering which was changed in #631. Fixes #679
### Problem Description I would like to be able to set the build context for an image in a Docker Compose file to a git repo URL. This does not...
It seems that the incorrectness is related to the number of objects of that type -- greater factor of error as the number of objects increases. ``` ruby 2.1.2 :012...
`:rows` should be applied to the entire result set. Instead `:rows` limits the rows _of each batch_. This behavior causes unexpected results, for example, in `find_each` when a `:rows` option...
Accessing `#resource` instantiates `@resource`. `#content_changed?` appears to assume that the existence of `@resource` indicates a change.
At least `original_name` and `mime_type`. > c.content.original_name > => "dscsi010010020.tif" > 2.1.5 :028 > c.content.original_name = "foo.tif" > => "foo.tif" > 2.1.5 :029 > c.content.changed? > => false > 2.1.5...
Current code will break b/c AT::Resource responds to :each. Patch https://github.com/projecthydra/active_fedora/blob/master/lib/active_fedora/attributes.rb#L99-L105 to account for this exception.
We have observed with IE 10 and 11 requests for PDF files Range headers like: ``` Range: bytes=846336-846847, 846848-847359, 847360-847871 [...] ``` The current code inherited from 7.x expects only...