idlesign / django-oauthost

Reusable application for Django, introducing OAuth2 server functionality.
https://github.com/idlesign/django-oauthost
BSD 3-Clause "New" or "Revised" License
25 stars 0 forks source link

Migrations pending to upload #4

Open JustDevZero opened 2 years ago

JustDevZero commented 2 years ago

Looks like there are some migrations pending to upload, if i add the latest version on pypi to a new project, and run 'makemigrations' it detects this new migration missing:


# Generated by Django 3.2.6 on 2021-12-02 21:27

from django.db import migrations, models

class Migration(migrations.Migration):

    dependencies = [
        ('oauthost', '0002_auto_20150927_1933'),
    ]

    operations = [
        migrations.AlterField(
            model_name='authorizationcode',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='client',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='redirectionendpoint',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='scope',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
        migrations.AlterField(
            model_name='token',
            name='id',
            field=models.BigAutoField(auto_created=True, primary_key=True, serialize=False, verbose_name='ID'),
        ),
    ]
idlesign commented 2 years ago

Thank you for the report. It might be because using DEFAULT_AUTO_FIELD setting globally for your project. Since AppConfig.default_auto_field is not defined [yet] for outhost, the global setting is used.

That said, not having this migration shouldn't have any impact on functionality.

JustDevZero commented 2 years ago

Ah, i see. Yeah, it's a brand new project, so I guess that's what happens here, it's relying on Django default values then.

-------- Mensaje original -------- On 3 dic. 2021 2:32, Igor Starikov < @.***> escribió:

Thank you for the report. It might be because using DEFAULT_AUTO_FIELD setting globally for your project. Since AppConfig.default_auto_field is not defined [yet] for outhost, the global setting is used.

That said, not having this migration shouldn't have any impact on functionality.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. AABKFVYTZCQVND7PIEI2AJTUPAM2DA5CNFSM5JIFY5QKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHK4AQUY.gif