Skip to content

Merge develop into master - #17

Open
StephenHulme wants to merge 42 commits into
masterfrom
develop
Open

Merge develop into master#17
StephenHulme wants to merge 42 commits into
masterfrom
develop

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

lgebhardt and others added 30 commits November 11, 2016 09:32
* If caching has been enabled, however disabled for a resource, the
  context values are nested in a a 'context' key. For example:
  { context: { foo: :bar } } vs { foo: :bar }

(cherry picked from commit 0936916)
…ation with partially preloaded relations, resolves JSONAPI-Resources#889

(cherry picked from commit d9d9d3f)
…n `_parser_exception`

(cherry picked from commit e144f80)
Fixes an issue where the recreated relationships might be using the wrong model_name if the model_name is changed in a resource that is derived from a non abstract resource, such as done in many of the tests.
Breaking change: Derived resources now use the model name of their base resource, if it is not abstract.
Cleans up the tests to not have the warnings about missing models.
Fixes issue in _model_class related to JSONAPI-Resources#952, and renames @model (class level) to @model_class to avoid confusion with instance level @model

Fixes JSONAPI-Resources#952, JSONAPI-Resources#654

(cherry picked from commit 280ccea)
* Added test and potential fix for JSONAPI-Resources#628.

* Add handling for CSV parsing errors.

(cherry picked from commit 9306ec0)
* Fix has_one polymorphism

* Add tests for has one polymorphic serialization

(cherry picked from commit 9ad4d91)
…ation with partially preloaded relations, resolves JSONAPI-Resources#889

(cherry picked from commit d9d9d3f)
Fixes JSONAPI-Resources#960

Potentially a breaking change for apps with guids

(cherry picked from commit 4f51331)
(cherry picked from commit 57fa0ae)
```
go get -u github.com/client9/misspell/cmd/misspell
misspell  -w -error -source=text .
```

(cherry picked from commit 726b102)
…i-resources gem to ensure compatibility with RubyGems and Bundler
…7.1.0 which are required for compatibility with Rails 7.1 and Ruby 3.x
seenanair and others added 12 commits June 16, 2025 16:31
…and < 3.0 (ensuring compatibility with both older and newer Ruby/Rails setups, while avoiding breaking changes introduced in Bundler 3.x.) ; add runtime dependency for csv (because Ruby 3.4+ no longer includes the csv library by default)
…recent Rails versions, replacing deprecated or invalid patterns to ensure proper table and index creation.
Y25-318 Publish gem as sanger-jsonapi-resources
…-to-fix-the-json-api-resource-incompatibility-with-rack-which-is-causing-422-errors-to-fail-with-a-status-of-0

Y25-319 - [PR] [Develop] Add compatibility for obsolete Rack status symbols
Adding CONTRIBUTING.md

Tests are failing but nothing to do with the changes to .md files here.
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.

DPL-936-5 - As developers we need to fork JSON API 0.9.0 so we can fix a minor issues so we can upgrade rails to 6.1 to apply the security fix