AppConfig Application Configuration - Configurable Attributes

 AppConfig:

  • Application Configuration objects store metadata for an application. Some attributes can be configured in AppConfig subclasses. 
  • Others are set by Django and read-only.

AppConfig.name: 

  • Full Python path to the application, ex. 'django.contrib.admin'.
  • AppConfig.name attribute defines which application the configuration applies to. 
  • It must be set in all AppConfig subclasses.
  • It must be unique across a Django project.

AppConfig.label: 
  • Short name for the application, ex. 'admin'
  • This attribute allows relabeling an application when two applications have conflicting labels. 
  • It defaults to the last component of name. 
  • It should be a valid Python identifier.
  • It must be unique across a Django project.

AppConfig.verbose_name:
  • Human Readable name for the Application, ex. “Administration”.
  • This attribute defaults to label.title().
AppConfig.path:
  • File System Path to the application directory, ex. '/usr/lib/pythonX.Y/dist-packages/django/contrib/admin'.
  • Django can automatically detect and set this, but we can also provide an explicit override as a class attribute on your AppConfig subclass. 
  • In a few situations this is required; for example if the app package is a namespace package with multiple paths.
AppConfig.default:
  • Set this attribute to False to prevent Django from selecting a configuration class automatically. 
  • This is useful when apps.py defines only one AppConfig subclass but you do not want Django to use it by default.
  • Set this attribute to True to tell Django to select a configuration class automatically. This is useful when apps.py defines more than one AppConfig subclass and you want Django to use one of them by default.
  • By default, this attribute isn’t set.
AppConfig.default_auto_field:
  • The implicit primary key type to add to models within this app. 
  • You can use this to keep AutoField as the primary key type for third party applications.
  • By default, this is the value of DEFAULT_AUTO_FIELD.

Comments

Post a Comment

Popular posts from this blog

Internationalization (Language Setting) in Django

If your project want to run in English and a Spanish version edit the settings.py file of your project and add the following LANGUAGES setting to it.  Place it next to the LANGUAGE_CODE setting:                LANGUAGES = (                ('en', 'English'),                ('es', 'Spanish'),              ) The LANGUAGES setting contains two tuples that consist of a language code and a name .  Language codes can be locale-specific , such as en-us or en-gb , or generic , such as en . With this setting, we specified that application will only be available in English and Spanish.  If you don't define a custom LANGUAGES setting, the site will be available in all the languages that Django is translated into. Make your LANGUAGE_CODE setting look as follows:            ...
Read more

reverse_lazy() Method in Django

Use reverse_lazy() to generate the URL for the link attribute. The reverse() method allows you to build URLs by their name and pass optional parameters. The reverse_lazy() utility function is a lazily evaluated version of reverse(). It allows you to use a URL reversal before the project's URL configuration is loaded.
Read more

CharFilter in Django

  CharFilter filter does simple character matches, used with CharField and TextField by default. ex: char_filter_field_name = CharFilter(field_name='char_filter_field_name', lookup_expr='icontains', label='Char Filter Field Name', widget=forms.TextInput(attrs={'class': 'col-md-12 mr-2','placeholder': 'Please Enter Char Filter Field Name', 'style': 'width: 263px'}))     
Read more