Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); GitHub - 3dcl/jsonapi-swagger: Create a JSONAPI Swagger. · GitHub
Skip to content

Repository files navigation

JSONAPI Swagger

Generate JSONAPI Swagger Doc.

Gem VersionGitHub license

jsonapi-swagger-4-2-9.gif

Installation

Add this line to your application's Gemfile:

gem'jsonapi-swagger'

And then execute:

$ bundle

Or install it yourself as:

$ gem install jsonapi-swagger

Usage

  1. config jsonapi swagger
# config/initializers/swagger.rbJsonapi::Swagger.configdo |config|
config.use_rswag=falseconfig.version='3.0.0'config.info={title: 'API V1',version: 'V1'}config.file_path='v1/swagger.json'end
  1. generate swagger.json
# gen swagger/v1/swagger.json
bundle exec rails generate jsonapi:swagger User # UserResource < JSONAPI::Resource
  1. additional

use rswag, have to run

# gen swagger/v1/swagger.json
bundle exec rails rswag:specs:swaggerize
  1. Adjust swagger_helper.rb

It must include the generated schema files into the openapi / swagger file to referenced

require"rails_helper"RSpec.configuredo |config|
# Specify a root folder where Swagger JSON files are generated# NOTE: If you're using the rswag-api to serve API descriptions, you'll need# to ensure that it's configured to serve Swagger from the same folderconfig.openapi_root=Rails.root.to_s + "/swagger"common_types=Rails.root.join("config","schemas","openapi","types","common_json_api.schema.json")schema_components=JSON.parse(File.read(common_types)).dig("components","schemas") || {}Dir.glob(Rails.root.join("config","schemas","openapi","types","**.schema.json")).eachdo |file|
resource_name=file.split("/").last.split(".").first# do not double include the jsonapi typesnextif(resource_name == "common_json_api")schema=JSON.parse(File.read(file))schema_components[resource_name]=schemaend# Define one or more Swagger documents and provide global metadata for each one# When you run the 'rswag:specs:to_swagger' rake task, the complete Swagger will# be generated at the provided relative path under swagger_root# By default, the operations defined in spec files are added to the first# document below. You can override this behavior by adding a swagger_doc tag to the# the root example_group in your specs, e.g. describe '...', swagger_doc: 'v2/swagger.json'config.openapi_specs={"v1/swagger.json"=>{openapi: "3.0.0",info: {title: "API V1",version: "v1"},components: {schemas: schema_components},paths: {},servers: [{"url": "{protocol}://{host}/api","variables": {"protocol": {"enum": ["https"],"default": "https"},"host": {"default": "www.example.com"}}}]}}end

Customization

Overriding Types in Resource Classes

If your resource adds attributes that do not map directly to a database column there are in general no type information attached. As a solution to generate matching json schemas and running specs a const can be defined on your resource class providing a hash with more type info.

Example for JSONAPI REsources

class ExampleResource < JSONAPI::Resource
attributes :subscribed,
:values,
:array_min_max
self.resource_attribute_type_info
{
subscribed: { type: :boolean},
values: {type: :array, # use items type to set the type of the array items
items_type: :float, comment: 'Explanatory comment, overrides stored database column comment'
},
# property of array items can be specified using items_properties
array_min_max: {
type: :array,
# when items_type is :object then items_properties are evaluated
items_type: :object,
items_properties: {
min: {
type: :number
},
max: {
type: :number
}
}
}
}
end
def subscribed
current_user = context[:current_user]
return nil if current_user.nil?
@model.subscribed_by?(current_user)
end
def values
# an array of numbers
@model.values
end
end

Before, After and POST / PATCH data

As it cannot be forseen what is necessary to create a certain resource, there are several methods to adjust the generated code to provide an individual setup for models and to accommodate your authentication / authorization framework

The generated code for before action before { ... }, after action after { ... } and data definition let(:data){ ... } are created using corresponding templates:

  • swagger_base.rb.erb - optional base data and defintions to put on top of each generated spec
  • swagger_before.rb.erb
  • swagger_after.rb.erb
  • swagger_data.rb.erb

It is possible to override them by creating corresponding custom files in lib/generators/jsonapi/swagger/templates

In case you need custom code per resource, create a custom file for resource that preceedes the general templates

  • swagger_before_{resources_name}.rb.erb
  • swagger_after_{resources_name}.rb.erb
  • swagger_data_{resources_name}.rb.erb

RoadMap

  • immutable resources
  • filter/sort resources
  • mutable resources
  • generate swagger.json without rswag

Resource

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/superiorlu/jsonapi-swagger.

About

Create a JSONAPI Swagger.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages