Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tronquer PRENOM, NOMUSAGE, NOMNAISSANCE #678

Closed
Tracked by #675
freesteph opened this issue Apr 4, 2024 · 0 comments
Closed
Tracked by #675

tronquer PRENOM, NOMUSAGE, NOMNAISSANCE #678

freesteph opened this issue Apr 4, 2024 · 0 comments
Assignees

Comments

@freesteph
Copy link
Collaborator

No description provided.

freesteph added a commit that referenced this issue Apr 4, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

Closes #678.

[1]: rails/rails#51494
freesteph added a commit that referenced this issue Apr 4, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

Closes #678.

[1]: rails/rails#51494
freesteph added a commit that referenced this issue Apr 4, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

It's also coherent with the custom :asp_date type which we use in a
couple places (ie: prestadoss.rb) and takes care of formatting a date
object in the format dictated by the ASP.

Closes #678.

[1]: rails/rails#51494
freesteph added a commit that referenced this issue Apr 4, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

It's also coherent with the custom :asp_date type which we use in a
couple places (ie: prestadoss.rb) and takes care of formatting a date
object in the format dictated by the ASP.

Closes #678.

[1]: rails/rails#51494
freesteph added a commit that referenced this issue Apr 8, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

It's also coherent with the custom :asp_date type which we use in a
couple places (ie: prestadoss.rb) and takes care of formatting a date
object in the format dictated by the ASP.

Closes #678.

[1]: rails/rails#51494
freesteph added a commit that referenced this issue Apr 8, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

It's also coherent with the custom :asp_date type which we use in a
couple places (ie: prestadoss.rb) and takes care of formatting a date
object in the format dictated by the ASP.

Closes #678.

[1]: rails/rails#51494
freesteph added a commit that referenced this issue Apr 8, 2024
Piggyback the `limit` option for ActiveModel's attribute method (which
might be a thing one day[1]) to chop the value of the string directly
on the XML-generating class.

This keeps the mapping classes in charge of translating our data into
the ASP stuff, semantically, but keeps the actual XML-maker in control
of the formatted length, which makes more sense to me: all the XML
tags have an associated length in the ASP documentation, so keeping it
as close as possible to the XML generation code is nicer.

It's also coherent with the custom :asp_date type which we use in a
couple places (ie: prestadoss.rb) and takes care of formatting a date
object in the format dictated by the ASP.

Closes #678.

[1]: rails/rails#51494
@freesteph freesteph self-assigned this Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant