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

Add Django 5.1 support, are updated fetch_points_of_sales, blocked field of PointOfSale & signals #221

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

AlexCernik
Copy link

@AlexCernik AlexCernik commented Aug 9, 2024

  1. En fetch_points_of_sales, los objetos PointOfSales solo se actualizan si sus campos han cambiado, en la primera llamada a fetch_points_of_sales, no se crean PointOfSales si estos vienen bloqueados.
  2. Se estableció el campo blocked con un valor predeterminado de False en el modelo PointOfSales.
  3. Se agregó soporte para Django 5.1.
  4. Se actualizó _get_storage_from_settings ya que en versiones Django >= 4.2 ya no se utiliza DEFAULT_FILE_STORAGE.
  5. Se añadieron signals para eliminar archivos antiguos del almacenamiento una vez se cambien de certificate y logo en TaxPayer.

tox.ini Show resolved Hide resolved
tox.ini Show resolved Hide resolved
pyproject.toml Show resolved Hide resolved
pyproject.toml Show resolved Hide resolved
Comment on lines +19 to +23
migrations.AlterField(
model_name='taxpayer',
name='logo',
field=models.ImageField(blank=True, help_text='A logo to use when generating printable receipts.', null=True, upload_to='afip/taxpayers/logos/', verbose_name='logo'),
),
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Qué cambio hubo en este campo?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No nada, al hacer makemigrations me salía el archivo de migración del campo logo y lo había puesto junto al de la alteración del campo bloqueado, me olvidé de separar eso. Y me olvidé de verificar si hace falta ese archivo de migración del campo logo o solo es un error mío.

django_afip/signals.py Show resolved Hide resolved
django_afip/models.py Show resolved Hide resolved
@WhyNotHugo
Copy link
Owner

El error con Python 3.8 no está relacionado a tus cambios y podés ignorarlo: #222

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

Successfully merging this pull request may close these issues.

2 participants