Skip to content

Merge master into develop - #18

Open
StephenHulme wants to merge 348 commits into
developfrom
master
Open

Merge master into develop#18
StephenHulme wants to merge 348 commits into
developfrom
master

Conversation

@StephenHulme

Copy link
Copy Markdown
Member

All Submissions:

  • I've checked to ensure there aren't other open Pull Requests for the same update/change.
  • I've submitted a ticket for my issue if one did not already exist.
  • My submission passes all tests. (Please run the full test suite locally to cut down on noise from travis failures.)
  • I've used Github auto-closing keywords in the commit message or the description.
  • I've added/updated tests for this change.

New Feature Submissions:

  • I've submitted an issue that describes this feature, and received the go ahead from the maintainers.
  • My submission includes new tests.
  • My submission maintains compliance with JSON:API.

Bug fixes and Changes to Core Features:

  • I've included an explanation of what the changes do and why I'd like you to include them.
  • I've provided test(s) that fails without the change.

Test Plan:

Reviewer Checklist:

  • Maintains compliance with JSON:API
  • Adequate test coverage exists to prevent regressions

dgeb and others added 30 commits May 4, 2017 22:00
…earlier

Tightens the error handling on request parsing.
…rphic-relationship-id

fix relationship linkage when it has overridden primary_key
…ter-respect-attribute-delegate

apply_filter and apply_sort respects :delegate option of attribute
Rails 4.2.8 now supports ruby 2.4
…skip_bug_reports

Skips the `test:bug_report_template:rails_5` in default task
# Conflicts:
#	lib/jsonapi/active_record_accessor.rb
…ationships

Fix nested namespaces parsing and resource resolving
…exceptions_from_callbacks

Handle exceptions from process_operations callbacks, remove :rollback callback
…rd_accessors

Refactor RecordAccessors to ResourceFinders
…d-filter-error-message

Use original key format when displaying error for filter not allowed
The existing tests are passing because they seem to all use a self-
referential `has_one` relationship. If the foreign_key is on a different
table, however, the queries will fail. So if it the relationship is a
has_one, we need to alter the query to look for the foreign-key on the
related table.
I think there was a little mistake in here, your probably meant
`context = options[:context]` instead of `context = context`
This solve an issue I had while fetching relationships
Fix a bug that occurs when fetching relationships
also fix sorting by has_many association

add tests

fix resource tests for building sort joins
seenanair and others added 30 commits June 18, 2025 10:15
Y25-318 Publish sanger-jsonapi-resources gem from master
…to-fix-the-json-api-resource-incompatibility-with-rack-which-is-causing-422-errors-to-fail-with-a-status-of-0

Y25-319 - [PR] [Master] Add compatibility for obsolete Rack status symbols
Fix for Rails 8.1 - updating the `Resource` instantiation with the latest API changes
Adding CONTRIBUTING.md - updating README contribution section.
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.