bridgetown-prismic 0.2.0 → 0.2.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c9490120f332e574829b9e86bb4e5cd8e116cc5d56459deaa6d008918d1259e7
-  data.tar.gz: 429b14738f5b6d15cee42b023085b71aa27ce69fcb9a108398efcabccc4aca33
+  metadata.gz: edc984dde8e51c56c4b6da117b7f0a16f5fb81ec966ff28b9424bde9c2bc7858
+  data.tar.gz: 3e553d7e6af94da3cf2590fe4b2301c1e368c7dfc95408898a41e0aa28438925
 SHA512:
-  metadata.gz: 847aebd7f01e975dead3b109ff69d65171da42d1f2a163b1ebf2fc26ffffc5b54db23949ab7027687b20d5b02da6266a1bcb6c90191343658ddfe138d1be1e52
-  data.tar.gz: 1d3cde2d78fcd09a22fa26b67caec953a8f9074b101079ead246f74f6e1c19936b405c9e3857c56c9d97eb7612f3f9d459c4dadabe62800b24fbc42ed6920df9
+  metadata.gz: ec881170fdaff8ef22f840cffd403b1dd4bcfa427bb858db4487e75a47c7b59ceb4e5a8b1135e850378f2c400761ceb81fb01893d5c6ba15c31cc26fb333d6c1
+  data.tar.gz: 124c223cdfc6ff567acd33c67e0986ac4d4a88ca05e881e7f0be160709393f5f085c7d108cb8d1f3014dd55d87862e716894fd13319d703e5590397c2bbfd60e

data/CHANGELOG.md

@@ -9,6 +9,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ...
 
+## 0.2.1
+
+- Fix issue where link resolvers didn't provide the full document
+
 ## 0.2.0
 
 - Automatically paginate through results sets

data/README.md

@@ -115,7 +115,7 @@ end
 * `collection_name`: this can be a built-in collection such as `posts` or `pages`, or it can be a custom collection you've configured in `bridgetown.config.yml`.
 * `prismic_custom_type`: this will be the "API ID" of the custom type in Prismic.
 * `prismic_slug`: this should return the "slug" (aka `my-document-title`) of a Prismic document. In this example the slug Prismic chose is being used verbatim, but you can make alterations as you see fit.
-* `prismic_url`: this should return the full URL of the final destination for the content. It should match the permalink settings of your collection. This is used by the "link resolver"—aka anywhere in a Prismic document where you've added a link to another Prismic document, the URL for that link to resolved using this return value for the custom type.
+* `prismic_url`: this should return the full URL of the final destination for the content. It should match the permalink settings of your collection. This is used by the "link resolver"—aka anywhere in a Prismic document where you've added a link to another Prismic document, the URL for that link is resolved using this return value for the custom type.
 
 All right, with those options out of the way, on to the main event:
 
@@ -141,7 +141,7 @@ end
 
 This where you create the 1:1 mappings between the Prismic fields and the "front matter" (aka data) + content of your model/resource. Any time you access the resource in templates by writing `resource.data.title` or `resource.content`, it will be pulling those values from these mappings.
 
-Within the `provide_data` block, you use a special Ruby DSL in a spreadsheet-like manner to set up the mappings. On the left-hand "column", you specify the name of the front matter variable (or content). In the middle column, you use Prismic's Ruby API to get a field value or metadata. On the right-hand column, you "coerce" the value into the type of data you'r looking for. Note that any field which the author hasn't filled in has a `nil` value, so you can see this is using Ruby's safe navigation operator `&` (whimsically known as the "lonely operator") most of the time so nil values won't crash the import process.
+Within the `provide_data` block, you use a special Ruby DSL in a spreadsheet-like manner to set up the mappings. On the left-hand "column", you specify the name of the front matter variable, as well as  `content` (optional but recommended). In the middle column, you use Prismic's Ruby API to get a field value or metadata. On the right-hand column, you "coerce" the value into the type of data you're looking for. Note that any field which the author hasn't filled in has a `nil` value, so you can see we're using Ruby's safe navigation operator `&` (whimsically known as the "lonely operator") most of the time so nil values won't crash the import process.
 
 You can [read more about Prismic's Ruby Document API here](https://prismic.io/docs/technologies/the-document-object-ruby) for information on when to use `value` or `as_text` or `url`, etc.
 
@@ -185,7 +185,7 @@ The Ruby DSL is pretty nifty, but you may occasionally run into a conflict betwe
 set :method, doc["page.method"].as_text
 ```
 
-Finally, if you decide to need to bail and want to provide a standard hash instead of using the Ruby DSL, you can do that too!
+Finally, if you decide to need to bail and want to provide a standard hash instead of using the Ruby DSL, you can do that too! It's not as flexible as the DSL because you can't arbitrarily insert multi-line statements of Ruby code within the data hash, but it's easy enough to understand:
 
 ```ruby
 def self.process_prismic_document(doc)

data/lib/bridgetown-prismic/api.rb

@@ -10,7 +10,12 @@ module BridgetownPrismic
         next "/preview/#{link.type}/#{link.id}" if site.config.prismic_preview_token
 
         if model_exists_for_prismic_type? link.type
-          model_for_prismic_type(link.type).prismic_url(link)
+          full_doc = Async do
+            Bridgetown::Current.site = site # ensure fiber has copy of the current site
+            site.config.prismic_api.getByID(link.id)
+          end.wait
+
+          model_for_prismic_type(link.type).prismic_url(full_doc)
         else
           "/"
         end

data/lib/bridgetown-prismic/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module BridgetownPrismic
-  VERSION = "0.2.0"
+  VERSION = "0.2.1"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: bridgetown-prismic
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.1
 platform: ruby
 authors:
 - Bridgetown Team