etiqueta_nutricional 5.0.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.coveralls.yml +1 -0
- data/.gitignore +10 -0
- data/.travis.yml +9 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +7 -0
- data/Gemfile.lock +111 -0
- data/Guardfile +82 -0
- data/README.md +24 -0
- data/Rakefile +6 -0
- data/bin/console +14 -0
- data/bin/setup +8 -0
- data/doc/CODE_OF_CONDUCT_md.html +194 -0
- data/doc/Etiqueta.html +972 -0
- data/doc/EtiquetaNutricional.html +110 -0
- data/doc/EtiquetaNutricional/Error.html +103 -0
- data/doc/Gemfile.html +103 -0
- data/doc/Gemfile_lock.html +179 -0
- data/doc/Guardfile.html +179 -0
- data/doc/Individuo.html +373 -0
- data/doc/ListaEtiquetas.html +605 -0
- data/doc/Object.html +117 -0
- data/doc/Paciente.html +521 -0
- data/doc/README_md.html +128 -0
- data/doc/Rakefile.html +100 -0
- data/doc/bin/setup.html +100 -0
- data/doc/created.rid +18 -0
- data/doc/css/fonts.css +167 -0
- data/doc/css/rdoc.css +590 -0
- data/doc/etiqueta_nutricional_gemspec.html +140 -0
- data/doc/fonts/Lato-Light.ttf +0 -0
- data/doc/fonts/Lato-LightItalic.ttf +0 -0
- data/doc/fonts/Lato-Regular.ttf +0 -0
- data/doc/fonts/Lato-RegularItalic.ttf +0 -0
- data/doc/fonts/SourceCodePro-Bold.ttf +0 -0
- data/doc/fonts/SourceCodePro-Regular.ttf +0 -0
- data/doc/images/add.png +0 -0
- data/doc/images/arrow_up.png +0 -0
- data/doc/images/brick.png +0 -0
- data/doc/images/brick_link.png +0 -0
- data/doc/images/bug.png +0 -0
- data/doc/images/bullet_black.png +0 -0
- data/doc/images/bullet_toggle_minus.png +0 -0
- data/doc/images/bullet_toggle_plus.png +0 -0
- data/doc/images/date.png +0 -0
- data/doc/images/delete.png +0 -0
- data/doc/images/find.png +0 -0
- data/doc/images/loadingAnimation.gif +0 -0
- data/doc/images/macFFBgHack.png +0 -0
- data/doc/images/package.png +0 -0
- data/doc/images/page_green.png +0 -0
- data/doc/images/page_white_text.png +0 -0
- data/doc/images/page_white_width.png +0 -0
- data/doc/images/plugin.png +0 -0
- data/doc/images/ruby.png +0 -0
- data/doc/images/tag_blue.png +0 -0
- data/doc/images/tag_green.png +0 -0
- data/doc/images/transparent.png +0 -0
- data/doc/images/wrench.png +0 -0
- data/doc/images/wrench_orange.png +0 -0
- data/doc/images/zoom.png +0 -0
- data/doc/index.html +116 -0
- data/doc/js/darkfish.js +161 -0
- data/doc/js/jquery.js +4 -0
- data/doc/js/navigation.js +142 -0
- data/doc/js/navigation.js.gz +0 -0
- data/doc/js/search.js +109 -0
- data/doc/js/search_index.js +1 -0
- data/doc/js/search_index.js.gz +0 -0
- data/doc/js/searcher.js +229 -0
- data/doc/js/searcher.js.gz +0 -0
- data/doc/table_of_contents.html +337 -0
- data/etiqueta_nutricional.gemspec +48 -0
- data/lib/etiqueta_nutricional.rb +13 -0
- data/lib/etiqueta_nutricional/array.rb +50 -0
- data/lib/etiqueta_nutricional/etiqueta_nutricional.rb +114 -0
- data/lib/etiqueta_nutricional/individuo.rb +39 -0
- data/lib/etiqueta_nutricional/lista_etiquetas.rb +198 -0
- data/lib/etiqueta_nutricional/menu.rb +66 -0
- data/lib/etiqueta_nutricional/paciente.rb +148 -0
- data/lib/etiqueta_nutricional/tabla.rb +45 -0
- data/lib/etiqueta_nutricional/version.rb +3 -0
- metadata +222 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA1:
|
3
|
+
metadata.gz: c37fc03f248579def7d4401bf05c3d9d01b722ff
|
4
|
+
data.tar.gz: 1568c3a2e58327e6fdba34918e3ce8463ecced36
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: d4783155f7e2e6fc9e75b17d2a507886243512bd26d8826713c483234cde3bdcba4b2979465a710d1ab292e3f4e7fcadf1243944b8901fa8c8a603bf6471f2c6
|
7
|
+
data.tar.gz: 63dba6925c59751e69e2b12848b2edd2c9762660978b4ef4137727b73c2add62e57937d109b47941681bb2d2ef786eec82ac60d75e0a5a03bc1d5cbad858ceb9
|
data/.coveralls.yml
ADDED
@@ -0,0 +1 @@
|
|
1
|
+
service_name: travis-ci
|
data/.gitignore
ADDED
data/.travis.yml
ADDED
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
* Using welcoming and inclusive language
|
18
|
+
* Being respectful of differing viewpoints and experiences
|
19
|
+
* Gracefully accepting constructive criticism
|
20
|
+
* Focusing on what is best for the community
|
21
|
+
* Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
* The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
* Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
* Public or private harassment
|
29
|
+
* Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
* Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at alu0100463118@ull.edu.es. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
data/Gemfile.lock
ADDED
@@ -0,0 +1,111 @@
|
|
1
|
+
PATH
|
2
|
+
remote: .
|
3
|
+
specs:
|
4
|
+
etiqueta_nutricional (5.0.0)
|
5
|
+
|
6
|
+
GEM
|
7
|
+
remote: https://rubygems.org/
|
8
|
+
specs:
|
9
|
+
coderay (1.1.2)
|
10
|
+
coveralls (0.7.1)
|
11
|
+
multi_json (~> 1.3)
|
12
|
+
rest-client
|
13
|
+
simplecov (>= 0.7)
|
14
|
+
term-ansicolor
|
15
|
+
thor
|
16
|
+
diff-lcs (1.3)
|
17
|
+
docile (1.3.1)
|
18
|
+
domain_name (0.5.20180417)
|
19
|
+
unf (>= 0.0.5, < 1.0.0)
|
20
|
+
ffi (1.9.25)
|
21
|
+
formatador (0.2.5)
|
22
|
+
guard (2.15.0)
|
23
|
+
formatador (>= 0.2.4)
|
24
|
+
listen (>= 2.7, < 4.0)
|
25
|
+
lumberjack (>= 1.0.12, < 2.0)
|
26
|
+
nenv (~> 0.1)
|
27
|
+
notiffany (~> 0.0)
|
28
|
+
pry (>= 0.9.12)
|
29
|
+
shellany (~> 0.0)
|
30
|
+
thor (>= 0.18.1)
|
31
|
+
guard-bundler (2.1.0)
|
32
|
+
bundler (~> 1.0)
|
33
|
+
guard (~> 2.2)
|
34
|
+
guard-compat (~> 1.1)
|
35
|
+
guard-compat (1.2.1)
|
36
|
+
guard-rspec (4.7.3)
|
37
|
+
guard (~> 2.1)
|
38
|
+
guard-compat (~> 1.1)
|
39
|
+
rspec (>= 2.99.0, < 4.0)
|
40
|
+
http-cookie (1.0.3)
|
41
|
+
domain_name (~> 0.5)
|
42
|
+
json (2.1.0)
|
43
|
+
listen (3.1.5)
|
44
|
+
rb-fsevent (~> 0.9, >= 0.9.4)
|
45
|
+
rb-inotify (~> 0.9, >= 0.9.7)
|
46
|
+
ruby_dep (~> 1.2)
|
47
|
+
lumberjack (1.0.13)
|
48
|
+
method_source (0.9.2)
|
49
|
+
mime-types (3.2.2)
|
50
|
+
mime-types-data (~> 3.2015)
|
51
|
+
mime-types-data (3.2018.0812)
|
52
|
+
multi_json (1.13.1)
|
53
|
+
nenv (0.3.0)
|
54
|
+
netrc (0.11.0)
|
55
|
+
notiffany (0.1.1)
|
56
|
+
nenv (~> 0.1)
|
57
|
+
shellany (~> 0.0)
|
58
|
+
pry (0.12.2)
|
59
|
+
coderay (~> 1.1.0)
|
60
|
+
method_source (~> 0.9.0)
|
61
|
+
rake (10.5.0)
|
62
|
+
rb-fsevent (0.10.3)
|
63
|
+
rb-inotify (0.9.10)
|
64
|
+
ffi (>= 0.5.0, < 2)
|
65
|
+
rest-client (2.0.2)
|
66
|
+
http-cookie (>= 1.0.2, < 2.0)
|
67
|
+
mime-types (>= 1.16, < 4.0)
|
68
|
+
netrc (~> 0.8)
|
69
|
+
rspec (3.7.0)
|
70
|
+
rspec-core (~> 3.7.0)
|
71
|
+
rspec-expectations (~> 3.7.0)
|
72
|
+
rspec-mocks (~> 3.7.0)
|
73
|
+
rspec-core (3.7.1)
|
74
|
+
rspec-support (~> 3.7.0)
|
75
|
+
rspec-expectations (3.7.0)
|
76
|
+
diff-lcs (>= 1.2.0, < 2.0)
|
77
|
+
rspec-support (~> 3.7.0)
|
78
|
+
rspec-mocks (3.7.0)
|
79
|
+
diff-lcs (>= 1.2.0, < 2.0)
|
80
|
+
rspec-support (~> 3.7.0)
|
81
|
+
rspec-support (3.7.1)
|
82
|
+
ruby_dep (1.5.0)
|
83
|
+
shellany (0.0.1)
|
84
|
+
simplecov (0.16.1)
|
85
|
+
docile (~> 1.1)
|
86
|
+
json (>= 1.8, < 3)
|
87
|
+
simplecov-html (~> 0.10.0)
|
88
|
+
simplecov-html (0.10.2)
|
89
|
+
term-ansicolor (1.7.0)
|
90
|
+
tins (~> 1.0)
|
91
|
+
thor (0.20.3)
|
92
|
+
tins (1.20.2)
|
93
|
+
unf (0.1.4)
|
94
|
+
unf_ext
|
95
|
+
unf_ext (0.0.7.5)
|
96
|
+
|
97
|
+
PLATFORMS
|
98
|
+
ruby
|
99
|
+
|
100
|
+
DEPENDENCIES
|
101
|
+
bundler (~> 1.17)
|
102
|
+
coveralls
|
103
|
+
etiqueta_nutricional!
|
104
|
+
guard
|
105
|
+
guard-bundler
|
106
|
+
guard-rspec
|
107
|
+
rake (~> 10.0)
|
108
|
+
rspec (~> 3.0)
|
109
|
+
|
110
|
+
BUNDLED WITH
|
111
|
+
1.17.1
|
data/Guardfile
ADDED
@@ -0,0 +1,82 @@
|
|
1
|
+
# A sample Guardfile
|
2
|
+
# More info at https://github.com/guard/guard#readme
|
3
|
+
|
4
|
+
## Uncomment and set this to only include directories you want to watch
|
5
|
+
# directories %w(app lib config test spec features) \
|
6
|
+
# .select{|d| Dir.exist?(d) ? d : UI.warning("Directory #{d} does not exist")}
|
7
|
+
|
8
|
+
## Note: if you are using the `directories` clause above and you are not
|
9
|
+
## watching the project directory ('.'), then you will want to move
|
10
|
+
## the Guardfile to a watched dir and symlink it back, e.g.
|
11
|
+
#
|
12
|
+
# $ mkdir config
|
13
|
+
# $ mv Guardfile config/
|
14
|
+
# $ ln -s config/Guardfile .
|
15
|
+
#
|
16
|
+
# and, you'll have to watch "config/Guardfile" instead of "Guardfile"
|
17
|
+
|
18
|
+
guard :bundler do
|
19
|
+
require 'guard/bundler'
|
20
|
+
require 'guard/bundler/verify'
|
21
|
+
helper = Guard::Bundler::Verify.new
|
22
|
+
|
23
|
+
files = ['Gemfile']
|
24
|
+
files += Dir['*.gemspec'] if files.any? { |f| helper.uses_gemspec?(f) }
|
25
|
+
|
26
|
+
# Assume files are symlinked from somewhere
|
27
|
+
files.each { |file| watch(helper.real_path(file)) }
|
28
|
+
end
|
29
|
+
|
30
|
+
# Note: The cmd option is now required due to the increasing number of ways
|
31
|
+
# rspec may be run, below are examples of the most common uses.
|
32
|
+
# * bundler: 'bundle exec rspec'
|
33
|
+
# * bundler binstubs: 'bin/rspec'
|
34
|
+
# * spring: 'bin/rspec' (This will use spring if running and you have
|
35
|
+
# installed the spring binstubs per the docs)
|
36
|
+
# * zeus: 'zeus rspec' (requires the server to be started separately)
|
37
|
+
# * 'just' rspec: 'rspec'
|
38
|
+
|
39
|
+
guard :rspec, cmd: "bundle exec rspec" do
|
40
|
+
require "guard/rspec/dsl"
|
41
|
+
dsl = Guard::RSpec::Dsl.new(self)
|
42
|
+
|
43
|
+
# Feel free to open issues for suggestions and improvements
|
44
|
+
|
45
|
+
# RSpec files
|
46
|
+
rspec = dsl.rspec
|
47
|
+
watch(rspec.spec_helper) { rspec.spec_dir }
|
48
|
+
watch(rspec.spec_support) { rspec.spec_dir }
|
49
|
+
watch(rspec.spec_files)
|
50
|
+
|
51
|
+
# Ruby files
|
52
|
+
ruby = dsl.ruby
|
53
|
+
dsl.watch_spec_files_for(ruby.lib_files)
|
54
|
+
|
55
|
+
# Rails files
|
56
|
+
rails = dsl.rails(view_extensions: %w(erb haml slim))
|
57
|
+
dsl.watch_spec_files_for(rails.app_files)
|
58
|
+
dsl.watch_spec_files_for(rails.views)
|
59
|
+
|
60
|
+
watch(rails.controllers) do |m|
|
61
|
+
[
|
62
|
+
rspec.spec.call("routing/#{m[1]}_routing"),
|
63
|
+
rspec.spec.call("controllers/#{m[1]}_controller"),
|
64
|
+
rspec.spec.call("acceptance/#{m[1]}")
|
65
|
+
]
|
66
|
+
end
|
67
|
+
|
68
|
+
# Rails config changes
|
69
|
+
watch(rails.spec_helper) { rspec.spec_dir }
|
70
|
+
watch(rails.routes) { "#{rspec.spec_dir}/routing" }
|
71
|
+
watch(rails.app_controller) { "#{rspec.spec_dir}/controllers" }
|
72
|
+
|
73
|
+
# Capybara features specs
|
74
|
+
watch(rails.view_dirs) { |m| rspec.spec.call("features/#{m[1]}") }
|
75
|
+
watch(rails.layouts) { |m| rspec.spec.call("features/#{m[1]}") }
|
76
|
+
|
77
|
+
# Turnip features and steps
|
78
|
+
watch(%r{^spec/acceptance/(.+)\.feature$})
|
79
|
+
watch(%r{^spec/acceptance/steps/(.+)_steps\.rb$}) do |m|
|
80
|
+
Dir[File.join("**/#{m[1]}.feature")][0] || "spec/acceptance"
|
81
|
+
end
|
82
|
+
end
|
data/README.md
ADDED
@@ -0,0 +1,24 @@
|
|
1
|
+
# EtiquetaNutricional
|
2
|
+
|
3
|
+
Practica 6 de la asignatura LPP. Desarrollo de una clase Etiqueta nutricional
|
4
|
+
|
5
|
+
## Instalacion
|
6
|
+
|
7
|
+
Añade esta line al gemfile de tu aplicacion
|
8
|
+
|
9
|
+
```ruby
|
10
|
+
gem 'etiqueta_nutricional'
|
11
|
+
```
|
12
|
+
|
13
|
+
y luego ejecuta:
|
14
|
+
|
15
|
+
$ bundle
|
16
|
+
|
17
|
+
O intalalo manualmente ejecutando:
|
18
|
+
|
19
|
+
$ gem install etiqueta_nutricional
|
20
|
+
|
21
|
+
## Uso
|
22
|
+
|
23
|
+
Nos permite crear etiquetas nutricionales para productos
|
24
|
+
|
data/Rakefile
ADDED
data/bin/console
ADDED
@@ -0,0 +1,14 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
require "bundler/setup"
|
4
|
+
require "etiqueta_nutricional"
|
5
|
+
|
6
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
7
|
+
# with your gem easier. You can also use a different console, if you like.
|
8
|
+
|
9
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
10
|
+
# require "pry"
|
11
|
+
# Pry.start
|
12
|
+
|
13
|
+
require "irb"
|
14
|
+
IRB.start(__FILE__)
|
data/bin/setup
ADDED
@@ -0,0 +1,194 @@
|
|
1
|
+
<!DOCTYPE html>
|
2
|
+
|
3
|
+
<html>
|
4
|
+
<head>
|
5
|
+
<meta charset="UTF-8">
|
6
|
+
|
7
|
+
<title>CODE_OF_CONDUCT - RDoc Documentation</title>
|
8
|
+
|
9
|
+
<script type="text/javascript">
|
10
|
+
var rdoc_rel_prefix = "./";
|
11
|
+
var index_rel_prefix = "./";
|
12
|
+
</script>
|
13
|
+
|
14
|
+
<script src="./js/jquery.js"></script>
|
15
|
+
<script src="./js/darkfish.js"></script>
|
16
|
+
|
17
|
+
<link href="./css/fonts.css" rel="stylesheet">
|
18
|
+
<link href="./css/rdoc.css" rel="stylesheet">
|
19
|
+
|
20
|
+
|
21
|
+
|
22
|
+
<body id="top" role="document" class="file">
|
23
|
+
<nav role="navigation">
|
24
|
+
<div id="project-navigation">
|
25
|
+
<div id="home-section" role="region" title="Quick navigation" class="nav-section">
|
26
|
+
<h2>
|
27
|
+
<a href="./index.html" rel="home">Home</a>
|
28
|
+
</h2>
|
29
|
+
|
30
|
+
<div id="table-of-contents-navigation">
|
31
|
+
<a href="./table_of_contents.html#pages">Pages</a>
|
32
|
+
<a href="./table_of_contents.html#classes">Classes</a>
|
33
|
+
<a href="./table_of_contents.html#methods">Methods</a>
|
34
|
+
</div>
|
35
|
+
</div>
|
36
|
+
|
37
|
+
<div id="search-section" role="search" class="project-section initially-hidden">
|
38
|
+
<form action="#" method="get" accept-charset="utf-8">
|
39
|
+
<div id="search-field-wrapper">
|
40
|
+
<input id="search-field" role="combobox" aria-label="Search"
|
41
|
+
aria-autocomplete="list" aria-controls="search-results"
|
42
|
+
type="text" name="search" placeholder="Search" spellcheck="false"
|
43
|
+
title="Type to search, Up and Down to navigate, Enter to load">
|
44
|
+
</div>
|
45
|
+
|
46
|
+
<ul id="search-results" aria-label="Search Results"
|
47
|
+
aria-busy="false" aria-expanded="false"
|
48
|
+
aria-atomic="false" class="initially-hidden"></ul>
|
49
|
+
</form>
|
50
|
+
</div>
|
51
|
+
|
52
|
+
</div>
|
53
|
+
|
54
|
+
|
55
|
+
<div class="nav-section">
|
56
|
+
<h3>Table of Contents</h3>
|
57
|
+
|
58
|
+
<ul class="link-list" role="directory">
|
59
|
+
<li><a href="#label-Contributor+Covenant+Code+of+Conduct">Contributor Covenant Code of Conduct</a>
|
60
|
+
<li><a href="#label-Our+Pledge">Our Pledge</a>
|
61
|
+
<li><a href="#label-Our+Standards">Our Standards</a>
|
62
|
+
<li><a href="#label-Our+Responsibilities">Our Responsibilities</a>
|
63
|
+
<li><a href="#label-Scope">Scope</a>
|
64
|
+
<li><a href="#label-Enforcement">Enforcement</a>
|
65
|
+
<li><a href="#label-Attribution">Attribution</a>
|
66
|
+
</ul>
|
67
|
+
</div>
|
68
|
+
|
69
|
+
|
70
|
+
<div id="project-metadata">
|
71
|
+
<div id="fileindex-section" class="nav-section">
|
72
|
+
<h3>Pages</h3>
|
73
|
+
|
74
|
+
<ul class="link-list">
|
75
|
+
|
76
|
+
<li><a href="./CODE_OF_CONDUCT_md.html">CODE_OF_CONDUCT</a>
|
77
|
+
|
78
|
+
<li><a href="./Gemfile.html">Gemfile</a>
|
79
|
+
|
80
|
+
<li><a href="./Gemfile_lock.html">Gemfile.lock</a>
|
81
|
+
|
82
|
+
<li><a href="./Guardfile.html">Guardfile</a>
|
83
|
+
|
84
|
+
<li><a href="./README_md.html">README</a>
|
85
|
+
|
86
|
+
<li><a href="./Rakefile.html">Rakefile</a>
|
87
|
+
|
88
|
+
<li><a href="./bin/setup.html">setup</a>
|
89
|
+
|
90
|
+
<li><a href="./etiqueta_nutricional_gemspec.html">etiqueta_nutricional.gemspec</a>
|
91
|
+
|
92
|
+
</ul>
|
93
|
+
</div>
|
94
|
+
|
95
|
+
</div>
|
96
|
+
</nav>
|
97
|
+
|
98
|
+
<main role="main" aria-label="Page CODE_OF_CONDUCT.md">
|
99
|
+
|
100
|
+
<h1 id="label-Contributor+Covenant+Code+of+Conduct">Contributor Covenant Code of Conduct<span><a href="#label-Contributor+Covenant+Code+of+Conduct">¶</a> <a href="#top">↑</a></span></h1>
|
101
|
+
|
102
|
+
<h2 id="label-Our+Pledge">Our Pledge<span><a href="#label-Our+Pledge">¶</a> <a href="#top">↑</a></span></h2>
|
103
|
+
|
104
|
+
<p>In the interest of fostering an open and welcoming environment, we as
|
105
|
+
contributors and maintainers pledge to making participation in our project
|
106
|
+
and our community a harassment-free experience for everyone, regardless of
|
107
|
+
age, body size, disability, ethnicity, gender identity and expression,
|
108
|
+
level of experience, nationality, personal appearance, race, religion, or
|
109
|
+
sexual identity and orientation.</p>
|
110
|
+
|
111
|
+
<h2 id="label-Our+Standards">Our Standards<span><a href="#label-Our+Standards">¶</a> <a href="#top">↑</a></span></h2>
|
112
|
+
|
113
|
+
<p>Examples of behavior that contributes to creating a positive environment
|
114
|
+
include:</p>
|
115
|
+
<ul><li>
|
116
|
+
<p>Using welcoming and inclusive language</p>
|
117
|
+
</li><li>
|
118
|
+
<p>Being respectful of differing viewpoints and experiences</p>
|
119
|
+
</li><li>
|
120
|
+
<p>Gracefully accepting constructive criticism</p>
|
121
|
+
</li><li>
|
122
|
+
<p>Focusing on what is best for the community</p>
|
123
|
+
</li><li>
|
124
|
+
<p>Showing empathy towards other community members</p>
|
125
|
+
</li></ul>
|
126
|
+
|
127
|
+
<p>Examples of unacceptable behavior by participants include:</p>
|
128
|
+
<ul><li>
|
129
|
+
<p>The use of sexualized language or imagery and unwelcome sexual attention or
|
130
|
+
advances</p>
|
131
|
+
</li><li>
|
132
|
+
<p>Trolling, insulting/derogatory comments, and personal or political attacks</p>
|
133
|
+
</li><li>
|
134
|
+
<p>Public or private harassment</p>
|
135
|
+
</li><li>
|
136
|
+
<p>Publishing others' private information, such as a physical or
|
137
|
+
electronic address, without explicit permission</p>
|
138
|
+
</li><li>
|
139
|
+
<p>Other conduct which could reasonably be considered inappropriate in a
|
140
|
+
professional setting</p>
|
141
|
+
</li></ul>
|
142
|
+
|
143
|
+
<h2 id="label-Our+Responsibilities">Our Responsibilities<span><a href="#label-Our+Responsibilities">¶</a> <a href="#top">↑</a></span></h2>
|
144
|
+
|
145
|
+
<p>Project maintainers are responsible for clarifying the standards of
|
146
|
+
acceptable behavior and are expected to take appropriate and fair
|
147
|
+
corrective action in response to any instances of unacceptable behavior.</p>
|
148
|
+
|
149
|
+
<p>Project maintainers have the right and responsibility to remove, edit, or
|
150
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
151
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
152
|
+
permanently any contributor for other behaviors that they deem
|
153
|
+
inappropriate, threatening, offensive, or harmful.</p>
|
154
|
+
|
155
|
+
<h2 id="label-Scope">Scope<span><a href="#label-Scope">¶</a> <a href="#top">↑</a></span></h2>
|
156
|
+
|
157
|
+
<p>This Code of Conduct applies both within project spaces and in public
|
158
|
+
spaces when an individual is representing the project or its community.
|
159
|
+
Examples of representing a project or community include using an official
|
160
|
+
project e-mail address, posting via an official social media account, or
|
161
|
+
acting as an appointed representative at an online or offline event.
|
162
|
+
Representation of a project may be further defined and clarified by project
|
163
|
+
maintainers.</p>
|
164
|
+
|
165
|
+
<h2 id="label-Enforcement">Enforcement<span><a href="#label-Enforcement">¶</a> <a href="#top">↑</a></span></h2>
|
166
|
+
|
167
|
+
<p>Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
168
|
+
reported by contacting the project team at alu0100463118@ull.edu.es. All
|
169
|
+
complaints will be reviewed and investigated and will result in a response
|
170
|
+
that is deemed necessary and appropriate to the circumstances. The project
|
171
|
+
team is obligated to maintain confidentiality with regard to the reporter
|
172
|
+
of an incident. Further details of specific enforcement policies may be
|
173
|
+
posted separately.</p>
|
174
|
+
|
175
|
+
<p>Project maintainers who do not follow or enforce the Code of Conduct in
|
176
|
+
good faith may face temporary or permanent repercussions as determined by
|
177
|
+
other members of the project's leadership.</p>
|
178
|
+
|
179
|
+
<h2 id="label-Attribution">Attribution<span><a href="#label-Attribution">¶</a> <a href="#top">↑</a></span></h2>
|
180
|
+
|
181
|
+
<p>This Code of Conduct is adapted from the <a
|
182
|
+
href="http://contributor-covenant.org">Contributor Covenant</a>, version
|
183
|
+
1.4, available at <a
|
184
|
+
href="http://contributor-covenant.org/version/1/4/">contributor-covenant.org/version/1/4</a></p>
|
185
|
+
</main>
|
186
|
+
|
187
|
+
|
188
|
+
|
189
|
+
<footer id="validator-badges" role="contentinfo">
|
190
|
+
<p><a href="http://validator.w3.org/check/referer">Validate</a>
|
191
|
+
<p>Generated by <a href="https://rdoc.github.io/rdoc">RDoc</a> 5.0.0.
|
192
|
+
<p>Based on <a href="http://deveiate.org/projects/Darkfish-RDoc/">Darkfish</a> by <a href="http://deveiate.org">Michael Granger</a>.
|
193
|
+
</footer>
|
194
|
+
|