insite 0.2.4 → 0.2.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a68396a261c66b3cb67524ff47c0bb3f6a17f21807d093175b1a73c293147eae
-  data.tar.gz: ea60b9b3bb3b67f566c9ca75346a886ba98e828298be6eb72989b07b91f930ee
+  metadata.gz: dc9b1b03c5b9ccb0c6cf3d4d64444318ebf3eb6528c0d48093d2e5018588325b
+  data.tar.gz: f3036582a4369c884d117bb2de34c6e8da66f5d1533c1f2c4c5740aa9f6fca74
 SHA512:
-  metadata.gz: 5a73e9efe53bc038eb8ff4b67269227ff34720b6aaa9060dadec600a9144bd7edcf9a132f700da5f1235afa291436a0ca096072f585516506a567cccfb831933
-  data.tar.gz: d175a8a0c4eb3829393b203a17c0fbd7c64ec327430afefeb71f12a6585b69eb10428c05f28b387757dff891a7681ff3a9c560b980d067395396e3743e0870c9
+  metadata.gz: f82dccd3aaf9d1991589621e26283f82348ca28fe49c98ccf80cabe208c85f7c61e04067dbac03525d6d4ec052f775de9b69b82aa169a3e71a0e4d571945f434
+  data.tar.gz: fcd84352557c0bb16e0c4b2b510ef552a6277897f6e168a170e6fad4e651480693d0023690b5084991796cf15e0dec81aea8f5d74c9c0b482dd7b9a616ceeabb

data/lib/insite/version.rb

@@ -1,3 +1,3 @@
 module Insite
-  VERSION = '0.2.4'
+  VERSION = '0.2.5'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: insite
 version: !ruby/object:Gem::Version
-  version: 0.2.4
+  version: 0.2.5
 platform: ruby
 authors:
 - John Fitisoff
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-11-17 00:00:00.000000000 Z
+date: 2018-11-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -164,17 +164,12 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: 3.7.0
-description: "Insite is a page object library that allows you to work with your website
-  in\na more natural way. It does this by providing a wrapper class for all of your\npages.
-  This wrapper (called a site object) functions as a sort of browser for\nyour page
-  objects. Benefits of this approach include simplified navigation \nand better error
-  handling when things go wrong.\n\nInsite also provides a highly portable, object
-  oriented approach to modeling\nrecurring features in your web application (e.g.,
-  cards, calendars, search \nwidgets, etc.) Components that you write are essentially
-  DOM extensions:\nThey can be referenced from other components or any standard DOM
-  object.\nThis interoperability with the DOM makes your component features more\naccessible
-  when writing tests and almost completely eliminates the need to\nwrite code to wire
-  your components up to pages or to get them to work with\nother components."
+description: |-
+  Page object library with an emphasis on simplified navigation and reusable code.
+  It has features geared towards supporting web components (www.webcomponents.org)
+  or any recurring feature in your application. UI automation components that you
+  define are extensions of the DOM and are fully interopable with standard DOM
+  elements and other components.
 email: jfitisoff@yahoo.com
 executables: []
 extensions: []
@@ -239,15 +234,9 @@ rubyforge_project:
 rubygems_version: 2.7.6
 signing_key: 
 specification_version: 4
-summary: 'Insite is a page object library that allows you to work with your website
-  in a more natural way. It does this by providing a wrapper class for all of your
-  pages. This wrapper (called a site object) functions as a sort of browser for your
-  page objects. Benefits of this approach include simplified navigation  and better
-  error handling when things go wrong.  Insite also provides a highly portable, object
-  oriented approach to modeling recurring features in your web application (e.g.,
-  cards, calendars, search  widgets, etc.) Components that you write are essentially
-  DOM extensions: They can be referenced from other components or any standard DOM
-  object. This interoperability with the DOM makes your component features more accessible
-  when writing tests and almost completely eliminates the need to write code to wire
-  your components up to pages or to get them to work with other components.'
+summary: Page object library with an emphasis on simplified navigation and reusable
+  code. It has features geared towards supporting web components (www.webcomponents.org)
+  or any recurring feature in your application. UI automation components that you
+  define are extensions of the DOM and are fully interopable with standard DOM elements
+  and other components.
 test_files: []