403Webshell
Server IP : 66.29.132.122  /  Your IP : 3.146.221.144
Web Server : LiteSpeed
System : Linux business142.web-hosting.com 4.18.0-553.lve.el8.x86_64 #1 SMP Mon May 27 15:27:34 UTC 2024 x86_64
User : admazpex ( 531)
PHP Version : 7.2.34
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : ON  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /proc/self/root/proc/self/root/proc/thread-self/root/proc/thread-self/root/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /proc/self/root/proc/self/root/proc/thread-self/root/proc/thread-self/root/opt/puppetlabs/puppet/lib/ruby/vendor_gems/gems/hocon-1.3.1/lib/hocon/config_mergeable.rb
# encoding: utf-8

require 'hocon'
require 'hocon/config_error'

#
# Marker for types whose instances can be merged, that is {@link Config} and
# {@link ConfigValue}. Instances of {@code Config} and {@code ConfigValue} can
# be combined into a single new instance using the
# {@link ConfigMergeable#withFallback withFallback()} method.
#
# <p>
# <em>Do not implement this interface</em>; it should only be implemented by
# the config library. Arbitrary implementations will not work because the
# library internals assume a specific concrete implementation. Also, this
# interface is likely to grow new methods over time, so third-party
# implementations will break.
#
module Hocon::ConfigMergeable
#
# Returns a new value computed by merging this value with another, with
# keys in this value "winning" over the other one.
#
# <p>
# This associative operation may be used to combine configurations from
# multiple sources (such as multiple configuration files).
#
# <p>
# The semantics of merging are described in the <a
# href="https://github.com/typesafehub/config/blob/master/HOCON.md">spec
# for HOCON</a>. Merging typically occurs when either the same object is
# created twice in the same file, or two config files are both loaded. For
# example:
#
# <pre>
#  foo = { a: 42 }
#  foo = { b: 43 }
# </pre>
#
# Here, the two objects are merged as if you had written:
#
# <pre>
#  foo = { a: 42, b: 43 }
# </pre>
#
# <p>
# Only {@link ConfigObject} and {@link Config} instances do anything in
# this method (they need to merge the fallback keys into themselves). All
# other values just return the original value, since they automatically
# override any fallback. This means that objects do not merge "across"
# non-objects; if you write
# <code>object.withFallback(nonObject).withFallback(otherObject)</code>,
# then <code>otherObject</code> will simply be ignored. This is an
# intentional part of how merging works, because non-objects such as
# strings and integers replace (rather than merging with) any prior value:
#
# <pre>
# foo = { a: 42 }
# foo = 10
# </pre>
#
# Here, the number 10 "wins" and the value of <code>foo</code> would be
# simply 10. Again, for details see the spec.
#
# @param other
#            an object whose keys should be used as fallbacks, if the keys
#            are not present in this one
# @return a new object (or the original one, if the fallback doesn't get
#         used)
#
  def with_fallback(other)
    raise Hocon::ConfigError::ConfigBugOrBrokenError, "subclasses of `ConfigMergeable` must implement `with_fallback` (#{self.class})"
  end
end

Youez - 2016 - github.com/yon3zu
LinuXploit