profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/tomciopp/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Thomas Cioppettini tomciopp Scalpel Software Inc Greenville, SC scalpel.com Trying to figure out why healthcare is expensive. Making software that increases efficiency in clinics across the country.

knrz/towel 78

A simple Maybe monad for Elixir.

bitwalker/alpine-erlang 76

An alpine image with Erlang installed, intended for releases

scalpel-software/cbor 15

Concise Binary Object Representation (RFC 7049)

tomciopp/checkpoint 4

Authorization library for Phoenix applications

scalpel-software/webauthn 3

Authenticate users to your web application using public key cryptography by becoming a webauthn relying party

tomciopp/demo_app 1

Demonstration Application

tomciopp/alpine-erlang 0

An alpine image with Erlang installed, intended for releases

tomciopp/apex 0

Awesome printing for Elixir

tomciopp/attr_encrypted 0

Generates attr_accessors that encrypt and decrypt attributes

tomciopp/audited 0

Audited (formerly acts_as_audited) is an ORM extension that logs all changes to your Rails models.

PR opened bitwalker/alpine-erlang

Erlang 24.1.2

@bitwalker Updates to OTP 24.1.2

https://erlang.org/download/OTP-24.1.2.README

+5 -5

0 comment

3 changed files

pr created time in 8 days

create barnchtomciopp/alpine-erlang

branch : erlang-24.1.2

created branch time in 8 days

PR opened lau/tzdata

chore(Default TZ data): Update to v2021c of the DB

@lau LMKWYT.

+0 -0

0 comment

1 changed file

pr created time in 9 days

create barnchtomciopp/tzdata

branch : update-tz-db

created branch time in 9 days

PR opened socialpaymentsbv/ex_phone_number

feat(ExPhoneNumber.Model.PhoneNumber): Add can_be_internationally_dia…

…lled?/1 with corresponding tests

Handles the can_be_internationally_dialled? function referenced in #43.

+38 -0

0 comment

2 changed files

pr created time in 9 days

create barnchtomciopp/ex_phone_number

branch : can-be-internationally-dialed

created branch time in 9 days

pull request commentsocialpaymentsbv/ex_phone_number

feat(ExPhoneNumber.Validation): Add is_possible_number_for_type?/2 an…

Handles some more of the missing implementation from issue #43.

tomciopp

comment created time in 9 days

PR opened socialpaymentsbv/ex_phone_number

feat(ExPhoneNumber.Validation): Add is_possible_number_for_type?/2 an…

…d is_possible_number_for_type_with_reason/2 with corresponding tests

There are going to be some additional failures in the test suite right now, but I believe they are due to issues with the implementation of methods that are called, not with the structure of the newly added code. I will take some time later to investigate fully.

+260 -1

0 comment

5 changed files

pr created time in 9 days

create barnchtomciopp/ex_phone_number

branch : is-possible-number-for-type

created branch time in 9 days

PR opened bitwalker/alpine-erlang

chore(Erlang): Update to version 24.1.1

@bitwalker Updates erlang to 24.1.1

https://erlang.org/download/OTP-24.1.README https://erlang.org/download/OTP-24.1.1.README

+4 -4

0 comment

2 changed files

pr created time in 17 days

create barnchtomciopp/alpine-erlang

branch : erlang-24.1.1

created branch time in 17 days

PR opened socialpaymentsbv/ex_phone_number

feat(ExPhoneNumber.Utilities#truncate_too_long_number/1): Add functio…

…n that can truncate too long phone numbers.

Adds the truncate_too_long_number method with corresponding tests as referenced in issue #43. Let me know if you have any questions or have any requests for changes.

+115 -0

0 comment

3 changed files

pr created time in 20 days

create barnchtomciopp/ex_phone_number

branch : truncate-too-long-number

created branch time in 20 days

push eventtomciopp/ex_phone_number

Thomas Cioppettini

commit sha cc64acc42a5312e32b360af0f5f3bacdf34c7cda

Unnecessarily quoted keyword (#23)

view details

Szymon Jeż

commit sha 4543a7b3ed7e41f839b3145961a279d590b46339

Update Copyright year

view details

JerryBels

commit sha 9fa347404af25a656386645cf3272524a77858d5

Update XML metadata to the last version, and code accordingly (#27)

view details

Szymon Jeż

commit sha 6493150cdf6cce6d3b346c1deb7cd1143e642ba7

Release version 0.1.2 (#29)

view details

Jose Miguel Rivero Bruno

commit sha 9d44cadb5769700949ad6250552ffa7afd261d3d

Prepare release v0.2.0 (#28)

view details

Szymon Jeż

commit sha 4f9a7107f86ae97963d65036a0a8e9699e51ad4d

Update Copyright Year

view details

Szymon Jeż

commit sha 2d1d3cd5e453809df6e1939fba365f753b405c0f

Update "Usage" output in README

view details

Suss Buzz

commit sha 05dcf1b8a7aa7291a1598323840a0d0acee017c3

Document parsing of e164 formatted numbers (#36)

view details

Jack Burns

commit sha 9191373a06444d6f5bb2d1a6b5ab85424f4f6e0d

Update parse to check invalid_length of stripped national number (#37)

view details

Szymon Jeż

commit sha 93a53efa03fcb821fdaacb261384b84b172428f9

Maintenance release 0.2.1 Bump version to 0.2.1

view details

Kian Meng Ang

commit sha 9ce6b204390d5d08094cb06cfc39ed9c285a7d11

Misc doc changes (#41)

view details

josemrb

commit sha 662bfd7e6b5334f2cb13dd2c9ed7cd1d6c55b1de

Update Validation * is_number_geographical/1

view details

josemrb

commit sha 42d151b7bf08be45280ea135246791606db780f7

Update Parsing * parse_helper/4 - Do not set empty preferred_domestic_carrier_code

view details

josemrb

commit sha 472e2ea994c6ba0c72ea735130d05f7269debcdd

Update Parsing * parse/2 - Add support to semicolon as extension character

view details

josemrb

commit sha ff60f4cd40978c061a4a724c8a32cd0c89c71601

Update Normalization + normalize_diallable_chars_only/1

view details

josemrb

commit sha 9340bc7e74d9808de43ebc0c74f06d33bf2fb67b

Update Model.PhoneNumber * get_national_significant_number/1 * set_italian_leading_zeros/2

view details

josemrb

commit sha 037c527a75399dd55003373b81b86d1f231afd9f

Updates ExtractionTest, FormattingTest * Remove unused alias

view details

josemrb

commit sha 886b2e9c8c687461c96929dcc664c6a2d8b2a32a

Update Resource XML metadata to v8.10.23

view details

josemrb

commit sha 9ee192e95e6746ebdfc18ec468c5fb40ad45a05d

Update ExtractionTest * Remove ExSpec * Update tests to v8.10.23 * Group tests according to JavaScript source code

view details

josemrb

commit sha a7469cb43dcb4652f38daec2bc9bc82807a11256

Update FormattingTest * Remove ExSpec * Update tests to v8.10.23 * Group tests according to JavaScript source code

view details

push time in 20 days

issue openedsocialpaymentsbv/ex_phone_number

Patch release

Any possibility of cutting a new release with the updated dependencies?

created time in 22 days

issue closedelixir-ecto/ecto

Ecto.Schema.validate_default!/2 happens at compile time

Environment

  • Elixir version (elixir -v): 1.12.3
  • Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): 13.4
  • Ecto version (mix deps): 3.7.0
  • Database adapter and version (mix deps): Postgrex 0.15.10
  • Operating system: OSX 11.6

Current behavior

Include code samples, errors and stacktraces if appropriate.

This issue was brought up in #3483 and the code was merged in #3487 but there is a corner case which I'm running into that causes my application to fail to compile when getting ready for production. We use a library that encrypts values before they are dumped to the DB. This library relies on a secret being available at runtime in order to process the custom type's dump function. Since the application does not have this value available at compile time, the code fails to compile and we cannot release new versions.

Expected behavior

I'm not 100% sure that this validation is necessary, but I'm sure @v0idpwn can give a legitimate reason as to why this fence should not be removed. When thinking about workarounds, I think the easiest option would be to create an escape valve within the validation if you have a legitimate reason to not check the default type. Something like skip_default_validation: true option should suffice. This way the previous behavior can be emulated and it is on the developer if they make a mistake. Let me know if you think of an alternative method to handle this issue or whether the added option field works. If that is good I can put together a PR and do some testing on my end to make sure everything is in working order.

closed time in a month

tomciopp

issue commentelixir-ecto/ecto

Ecto.Schema.validate_default!/2 happens at compile time

Fixed by #3749

tomciopp

comment created time in a month

pull request commentelixir-ecto/ecto

feat(Ecto.Schema): Add option to skip validations for default values

@josevalim I put it at the bottom since it is likely going to be the least used option for a field.

tomciopp

comment created time in a month

push eventtomciopp/ecto

Thomas Cioppettini

commit sha f0ee8bff3817cf6e3479da74ca1d1415dadfdbe8

docs(Ecto.Schema): Add documentation for the new :skip_default_validation option

view details

push time in a month

PR opened elixir-ecto/ecto

feat(Ecto.Schema): Add option to skip validations for default values

@josevalim Addresses Issue #3747. Let me know if you need any additional changes or want to add documentation for this feature.

+14 -2

0 comment

2 changed files

pr created time in a month

create barnchtomciopp/ecto

branch : skip-default-validations

created branch time in a month

issue commentelixir-ecto/ecto

Ecto.Schema.validate_default!/2 happens at compile time

@josevalim Yeah sure you should expect something in the next 24 hrs.

tomciopp

comment created time in a month

issue commentelixir-ecto/ecto

Ecto.Schema.validate_default!/2 happens at compile time

@josevalim It's usually an integer, sometimes it's a string. I could live in that world, although I'm not particularly in love with the idea of warnings that I know I will never be able to address. When I see a warning, my general response is to fix the code that has been deprecated. Ideally I want to live warning free, since a warning is a hint that I'm doing something wrong. In this case I want to tell ecto, "nah man it's cool don't worry about it, I got this"

tomciopp

comment created time in a month

issue openedelixir-ecto/ecto

Ecto.Schema.validate_default!/2 happens at compile time

Precheck

  • Do not use the issues tracker for help or support requests (try Elixir Forum, Stack Overflow, IRC or mailing lists, etc).
  • For proposing a new feature, please start a discussion on elixir-ecto.
  • For bugs, do a quick search and make sure the bug has not yet been reported.
  • Finally, be nice and have fun!

Environment

  • Elixir version (elixir -v): 1.12.3
  • Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): 13.4
  • Ecto version (mix deps): 3.7.0
  • Database adapter and version (mix deps): Postgrex 0.15.10
  • Operating system: OSX 11.6

Current behavior

Include code samples, errors and stacktraces if appropriate.

This issue was brought up in #3483 and the code was merged in #3487 but there is a corner case which I'm running into that causes my application to fail to compile when getting ready for production. We use a library that encrypts values before they are dumped to the DB. This library relies on a secret being available at runtime in order to process the custom type's dump function. Since the application does not have this value available at compile time, the code fails to compile and we cannot release new versions.

Expected behavior

I'm not 100% sure that this validation is necessary, but I'm sure @v0idpwn can give a legitimate reason as to why this fence should not be removed. When thinking about workarounds, I think the easiest option would be to create an escape valve within the validation if you have a legitimate reason to not check the default type. Something like skip_default_validation: true option should suffice. This way the previous behavior can be emulated and it is on the developer if they make a mistake. Let me know if you think of an alternative method to handle this issue or whether the added option field works. If that is good I can put together a PR and do some testing on my end to make sure everything is in working order.

created time in a month

PR opened bitwalker/alpine-erlang

chore(Erlang): Support otp v23.3.4.7

@bitwalker https://erlang.org/download/OTP-23.3.4.7.README

+3 -3

0 comment

2 changed files

pr created time in a month

create barnchtomciopp/alpine-erlang

branch : erlang-23.3.4.7

created branch time in a month

push eventscalpel-software/cbor

Kian-Meng, Ang

commit sha b81571c1e6753c73234b29c651f9081240713190

docs(README): misc doc changes Besides other documentation changes, this commit ensures the generated HTML doc for HexDocs.pm will become the source of truth for this Elixir library and leverage on latest features of ExDoc.

view details

push time in a month

PR merged scalpel-software/cbor

docs(README): misc doc changes

Besides other documentation changes, this commit ensures the generated HTML doc for HexDocs.pm will become the source of truth for this Elixir library and leverage on latest features of ExDoc.

+111 -68

1 comment

7 changed files

kianmeng

pr closed time in a month