mirror of https://github.com/abpframework/abp.git
Engincan VESKE
3 years ago
committed by
GitHub
GitHub
497 changed files with 7308 additions and 3162 deletions
@ -0,0 +1,52 @@ |
|||
import os |
|||
import json |
|||
from github import Github |
|||
|
|||
def update_latest_versions(): |
|||
version = os.environ["GITHUB_REF"].split("/")[-1] |
|||
|
|||
if "rc" in version: |
|||
return False |
|||
|
|||
with open("latest-versions.json", "r") as f: |
|||
latest_versions = json.load(f) |
|||
|
|||
latest_versions[0]["version"] = version |
|||
|
|||
with open("latest-versions.json", "w") as f: |
|||
json.dump(latest_versions, f, indent=2) |
|||
|
|||
return True |
|||
|
|||
def create_pr(): |
|||
g = Github(os.environ["GITHUB_TOKEN"]) |
|||
repo = g.get_repo("abpframework/abp") |
|||
|
|||
branch_name = f"update-latest-versions-{os.environ['GITHUB_REF'].split('/')[-1]}" |
|||
base = repo.get_branch("dev") |
|||
repo.create_git_ref(ref=f"refs/heads/{branch_name}", sha=base.commit.sha) |
|||
|
|||
# Get the current latest-versions.json file and its sha |
|||
contents = repo.get_contents("latest-versions.json", ref="dev") |
|||
file_sha = contents.sha |
|||
|
|||
# Update the file in the repo |
|||
repo.update_file( |
|||
path="latest-versions.json", |
|||
message=f"Update latest-versions.json to version {os.environ['GITHUB_REF'].split('/')[-1]}", |
|||
content=open("latest-versions.json", "r").read().encode("utf-8"), |
|||
sha=file_sha, |
|||
branch=branch_name, |
|||
) |
|||
|
|||
pr = repo.create_pull(title="Update latest-versions.json", |
|||
body="Automated PR to update the latest-versions.json file.", |
|||
head=branch_name, base="dev") |
|||
|
|||
pr.create_review_request(reviewers=["ebicoglu", "gizemmutukurt", "skoc10"]) |
|||
|
|||
if __name__ == "__dev__": |
|||
should_create_pr = update_latest_versions() |
|||
if should_create_pr: |
|||
create_pr() |
|||
|
|||
@ -0,0 +1,33 @@ |
|||
name: Update Latest Versions |
|||
|
|||
on: |
|||
release: |
|||
types: |
|||
- published |
|||
|
|||
permissions: |
|||
contents: write |
|||
pull-requests: write |
|||
|
|||
jobs: |
|||
update-versions: |
|||
runs-on: ubuntu-latest |
|||
steps: |
|||
- name: Checkout repository |
|||
uses: actions/checkout@v2 |
|||
|
|||
- name: Set up Python |
|||
uses: actions/setup-python@v2 |
|||
with: |
|||
python-version: 3.x |
|||
|
|||
- name: Install dependencies |
|||
run: | |
|||
python -m pip install --upgrade pip |
|||
pip install PyGithub |
|||
|
|||
- name: Update latest-versions.json and create PR |
|||
env: |
|||
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |
|||
run: | |
|||
python .github/scripts/update_versions.py |
|||
@ -0,0 +1,94 @@ |
|||
# Contributor Covenant Code of Conduct |
|||
|
|||
## Preamble |
|||
|
|||
The ABP Framework was created to implement common generic web application features in a common code base. This approach helps developers to decouple line of business application features from their custom business logic. Besides, the ABP Framework helps create MVPs and kick-start your project as quickly as possible. All the contributors try to save valuable time by automating repetitive tasks at the framework level. This code of conduct has been adopted by many [other open source communities](http://contributor-covenant.org/adopters/) and we feel it expresses our values well. |
|||
|
|||
|
|||
|
|||
## Our Pledge |
|||
|
|||
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community. |
|||
|
|||
|
|||
|
|||
## Our Standards |
|||
|
|||
Examples of behavior that contributes to a positive environment for our community include: |
|||
|
|||
- Demonstrating empathy and kindness toward other people |
|||
- Being respectful of differing opinions, viewpoints, and experiences |
|||
- Giving and gracefully accepting constructive feedback |
|||
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience |
|||
- Focusing on what is best not just for us as individuals but for the overall community |
|||
|
|||
Examples of unacceptable behavior include: |
|||
|
|||
- The use of sexualized language or imagery, and sexual attention or advances of any kind |
|||
- Trolling, insulting or derogatory comments, and personal or political attacks |
|||
- Public or private harassment |
|||
- Publishing others’ private information, such as a physical or email address, without their explicit permission |
|||
- Other conduct which could reasonably be considered inappropriate in a professional setting |
|||
|
|||
|
|||
|
|||
## Enforcement Responsibilities |
|||
|
|||
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. |
|||
|
|||
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned with this Code of Conduct and will communicate reasons for moderation decisions when appropriate. |
|||
|
|||
|
|||
|
|||
## Scope |
|||
|
|||
This Code of Conduct applies within all community spaces and when an individual officially represents the community in public spaces. Examples of representing our community include: |
|||
|
|||
- Using an official e-mail address. |
|||
- Posting via an official social media account. |
|||
- Acting as an appointed representative at an online or offline event. |
|||
|
|||
|
|||
|
|||
## Enforcement |
|||
|
|||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [info@abp.io](mailto:info@abp.io). All complaints will be reviewed and investigated promptly and fairly. All community leaders must to respect the privacy and security of the reporter of any incident. |
|||
|
|||
|
|||
|
|||
## Enforcement Guidelines |
|||
|
|||
Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: |
|||
|
|||
### 1. Correction |
|||
|
|||
**Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. |
|||
|
|||
**Consequence:** A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. |
|||
|
|||
### 2. Warning |
|||
|
|||
**Community Impact:** A violation through a single incident or series of actions. |
|||
|
|||
**Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period. This includes avoiding interactions in community spaces and external channels like social media. Violating these terms may lead to a temporary or permanent ban. |
|||
|
|||
### 3. Temporary Ban |
|||
|
|||
**Community Impact:** A serious violation of community standards, including sustained inappropriate behavior. |
|||
|
|||
**Consequence:** A temporary ban from any interaction or public communication with the community for a specified period. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. |
|||
|
|||
### 4. Permanent Ban |
|||
|
|||
**Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. |
|||
|
|||
**Consequence:** A permanent ban from any sort of public interaction within the community. |
|||
|
|||
|
|||
|
|||
## Attribution |
|||
|
|||
This document is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/), version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html. |
|||
Community Impact Guidelines were inspired by [Mozilla’s code of conduct enforcement ladder](https://github.com/mozilla/diversity). |
|||
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. |
|||
Translations are available at https://www.contributor-covenant.org/translations. |
|||
|
Before Width: | Height: | Size: 10 KiB After Width: | Height: | Size: 10 KiB |
|
Before Width: | Height: | Size: 30 KiB After Width: | Height: | Size: 30 KiB |
|
Before Width: | Height: | Size: 26 KiB After Width: | Height: | Size: 26 KiB |
|
Before Width: | Height: | Size: 4.4 KiB After Width: | Height: | Size: 4.4 KiB |
|
Before Width: | Height: | Size: 25 KiB After Width: | Height: | Size: 25 KiB |
|
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 13 KiB |
|
Before Width: | Height: | Size: 12 KiB After Width: | Height: | Size: 12 KiB |
|
Before Width: | Height: | Size: 7.2 KiB After Width: | Height: | Size: 7.2 KiB |
|
Before Width: | Height: | Size: 21 KiB After Width: | Height: | Size: 21 KiB |
|
Before Width: | Height: | Size: 19 KiB After Width: | Height: | Size: 19 KiB |
|
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
|
Before Width: | Height: | Size: 57 KiB After Width: | Height: | Size: 57 KiB |
|
Before Width: | Height: | Size: 613 KiB After Width: | Height: | Size: 613 KiB |
|
Before Width: | Height: | Size: 523 KiB After Width: | Height: | Size: 523 KiB |
|
Before Width: | Height: | Size: 40 KiB After Width: | Height: | Size: 40 KiB |
@ -0,0 +1,211 @@ |
|||
# ABP.IO Platform 7.2 RC Has Been Released |
|||
|
|||
Today, we are happy to release the [ABP Framework](https://abp.io/) and [ABP Commercial](https://commercial.abp.io/) version **7.2 RC** (Release Candidate). This blog post introduces the new features and important changes in this new version. |
|||
|
|||
Try this version and provide feedback for a more stable version of ABP v7.2! Thanks to all of you. |
|||
|
|||
## Get Started with the 7.2 RC |
|||
|
|||
Follow the steps below to try version 7.2.0 RC today: |
|||
|
|||
1) **Upgrade** the ABP CLI to version `7.2.0-rc.1` using a command line terminal: |
|||
|
|||
````bash |
|||
dotnet tool update Volo.Abp.Cli -g --version 7.2.0-rc.1 |
|||
```` |
|||
|
|||
**or install** it if you haven't before: |
|||
|
|||
````bash |
|||
dotnet tool install Volo.Abp.Cli -g --version 7.2.0-rc.1 |
|||
```` |
|||
|
|||
2) Create a **new application** with the `--preview` option: |
|||
|
|||
````bash |
|||
abp new BookStore --preview |
|||
```` |
|||
|
|||
See the [ABP CLI documentation](https://docs.abp.io/en/abp/latest/CLI) for all the available options. |
|||
|
|||
> You can also use the [Get Started](https://abp.io/get-started) page to generate a CLI command to create a new application. |
|||
|
|||
You can use any IDE that supports .NET 7.x, like [Visual Studio 2022](https://visualstudio.microsoft.com/downloads/). |
|||
|
|||
## Migration Guides |
|||
|
|||
There are breaking changes in this version that may affect your application. |
|||
Please see the following migration documents, if you are upgrading from v7.1: |
|||
|
|||
* [ABP Framework 7.1 to 7.2 Migration Guide](https://docs.abp.io/en/abp/7.2/Migration-Guides/Abp-7_2) |
|||
* [ABP Commercial 7.1 to 7.2 Migration Guide](https://docs.abp.io/en/commercial/7.2/migration-guides/v7_2) |
|||
|
|||
|
|||
## What's New with ABP Framework 7.2? |
|||
|
|||
In this section, I will introduce some major features released in this version. Here is a brief list of the titles that will be explained in the next sections: |
|||
|
|||
* Grouping of Navigation Menu Items |
|||
* Introducing the `BlazorWebAssemblyCurrentApplicationConfigurationCacheResetService` |
|||
* CMS Kit Comments: Don't Allow External URLs |
|||
* Angular UI New Components |
|||
* Others |
|||
|
|||
### Grouping of Navigation Menu Items |
|||
|
|||
Some applications may need to group their main menus to tidy up their menu structure. For example, you may want to group ABP's menu items, which came from modules in a group named *Admin*. |
|||
|
|||
In this version, you can allow to define groups and associate menu items with a group. Then your theme can render your menu items within the specified groups. |
|||
|
|||
**Example:** |
|||
|
|||
```csharp |
|||
private async Task ConfigureMainMenuAsync(MenuConfigurationContext context) |
|||
{ |
|||
//Creating a new group |
|||
context.Menu.AddGroup("Dashboards", l["Dashboards"]); |
|||
|
|||
//Setting the group name for menu items |
|||
context.Menu |
|||
.AddItem(new ApplicationMenuItem("Home", l["Menu:Home"], groupName: "Dashboards") |
|||
.AddItem(new ApplicationMenuItem("Home", l["Menu:Dashboard"], groupName: "Dashboards"); |
|||
} |
|||
``` |
|||
|
|||
> **Note**: Currently, only the [LeptonX Theme](https://leptontheme.com/) renders groups for menu items. See the "LeptonX - Render Groups for Menu Items" section below for a demonstration. |
|||
|
|||
### Introducing the `BlazorWebAssemblyCurrentApplicationConfigurationCacheResetService` |
|||
|
|||
In this version, we have introduced the `BlazorWebAssemblyCurrentApplicationConfigurationCacheResetService` service to re-initialize application configurations. This service can be helpful, if you want to reset the application configurations after changing some configurations through your code. For example, you might have changed the values of some settings and might want to be able to get the new settings without the need to refresh the page. For this purpose, the `BlazorWebAssemblyCurrentApplicationConfigurationCacheResetService.ResetAsync()` method can be used to re-initialize the application configurations and cache the updated configurations for further usages. |
|||
|
|||
> For more information, please see [https://github.com/abpframework/abp/issues/15887](https://github.com/abpframework/abp/issues/15887). |
|||
|
|||
### CMS Kit Comments: Disallowing External URLs |
|||
|
|||
CMS Kit provides a [comment system](https://docs.abp.io/en/abp/7.2/Modules/Cms-Kit/Comments) to add the comment feature to any kind of resource, like blog posts for an example. The CMS Kit comment section is good for visitor comments and can improve your interaction with your application users. |
|||
|
|||
Sometimes, malicious users (or bots) can submit advertisement links into the comment sections. With this version, you can specify *allowed external URLs* for a specific comment section and disallow any other external URLs. You just need to configure the `CmsKitCommentOptions` as follows: |
|||
|
|||
```csharp |
|||
Configure<CmsKitCommentOptions>(options => |
|||
{ |
|||
options.AllowedExternalUrls = new Dictionary<string, List<string>> |
|||
{ |
|||
{ |
|||
"Product", |
|||
new List<string> |
|||
{ |
|||
"https://abp.io/" |
|||
} |
|||
} |
|||
}; |
|||
}); |
|||
``` |
|||
|
|||
If you don't specify any allowed external URLs for a specific comment section, all external URLs are allowed to be used in comments. For more information, please refer to the [CMS Kit: Comments documentation](https://docs.abp.io/en/abp/latest/Modules/Cms-Kit/Comments). |
|||
|
|||
### New Components for Angular UI |
|||
|
|||
In this version, we have created some useful UI components for Angular UI, which are `abp-checkbox`, `abp-form-input`, and `abp-card`. Instead of using the related HTML elements and specifying bootstrap classes, from this version on, you can use these components. |
|||
|
|||
You can see the following examples for the usage of the `abp-card` component: |
|||
|
|||
```html |
|||
<abp-card cardClass="mt-4 mb-5"> |
|||
<abp-card-body> |
|||
<div>...</div> |
|||
</abp-card-body> |
|||
</abp-card> |
|||
``` |
|||
|
|||
> See the [Card Component documentation](https://docs.abp.io/en/abp/7.2/UI/Angular/Card-Component) for more information. |
|||
|
|||
### Others |
|||
|
|||
* OpenIddict registered custom scopes have been added to the openid-configuration endpoint (`/.well-known/openid-configuration`) automatically. See [#16141](https://github.com/abpframework/abp/issues/16141) for more information. |
|||
* Two new tag-helpers have been added to MVC UI, which are `abp-date-picker` and `abp-date-range-picker`. See [#15806](https://github.com/abpframework/abp/pull/15806) for more information. |
|||
* Filtering/searching has been improved in the Docs Module and unified under a single *Search* section. See [#15787](https://github.com/abpframework/abp/issues/15787) for more information. |
|||
|
|||
## What's New with ABP Commercial 7.2? |
|||
|
|||
We've also worked on [ABP Commercial](https://commercial.abp.io/) to align the features and changes made in the ABP Framework. The following sections introduce a few new features coming with ABP Commercial 7.2. |
|||
|
|||
### Authority Delegation |
|||
|
|||
Authority Delegation is a way of delegating the responsibility of the current user to a different user(s) for a limited time. Thus, a user can be switched to the delegated users' account and perform actions on their behalf. |
|||
|
|||
This version introduces support for the **Authority Delegation** in the [Account Module](https://docs.abp.io/en/commercial/latest/modules/account). You can check the following gif for a demonstration: |
|||
|
|||
 |
|||
|
|||
### Force Password Change at Next Logon |
|||
|
|||
It's a typical need to force users to change their password after their first successful login. Especially, if you as admin create a new user (*from the Users page of the Identity Pro module*, for example) with an easy initial password or a randomly generated password. The user should change his/her password with a more secure password that only they know. |
|||
|
|||
In this version, the "Forcing Password Change at Next Logon" feature has been added for this kind of purpose. Now, it's possible to force a user to change their password on the next login. |
|||
|
|||
The admin only needs to check the *Should change password on next login* option, while creating a new user: |
|||
|
|||
 |
|||
|
|||
After the first successful login, a password change page will open and force the user to change their password: |
|||
|
|||
 |
|||
|
|||
Then, the user starts using their account with a secure password that only they know. |
|||
|
|||
### Periodic Password Changes (Password Aging) |
|||
|
|||
**Password aging** is a mechanism to force users to periodically change their passwords. It allows you to specify a max number of days that a password can be used before it has to be changed. |
|||
|
|||
 |
|||
|
|||
You can force this behavior in the "Password renewing settings" section of the Settings page as can be seen in the image above. Then, after the specified time has passed, users will have to renew their passwords. |
|||
|
|||
### LeptonX - Render Groups for Menu Items |
|||
|
|||
As mentioned in the *Grouping of Navigation Menu Items* section above, the [LeptonX Theme](https://leptontheme.com/) renders groups for menu items: |
|||
|
|||
 |
|||
|
|||
### Suite: Show Properties on Create/Update/List Pages |
|||
|
|||
In this version, ABP Suite allows you to choose whether a property is visible/invisible on the create/update modals and list page. It also allows you to set specific properties to *readonly* on the update modals. |
|||
|
|||
 |
|||
|
|||
## Community News |
|||
|
|||
### ABP - DOTNET CONF'23 |
|||
|
|||
 |
|||
|
|||
As the ABP team, we've organized 10+ [online events](https://community.abp.io/events) and gained a good experience with software talks. We are organizing ABP Dotnet Conference 2023, a full-featured software conference, in May. You can visit [https://abp.io/conference](https://abp.io/conference) to see speakers, talks, schedules, and other details. |
|||
|
|||
**Less than a month left until the event**! Don't forget to take your seat and buy an early bird ticket from [https://kommunity.com/volosoft/events/1st-abp-conference-96db1a54](https://kommunity.com/volosoft/events/1st-abp-conference-96db1a54)! |
|||
|
|||
### New ABP Community Posts |
|||
|
|||
There are exciting articles contributed by the ABP community as always. I will highlight some of them here: |
|||
|
|||
* [What’s New in .NET 8 🧐 ? Discover ALL .NET 8 Features](https://community.abp.io/posts/whats-new-in-.net-8-discover-all-.net-8-features-llcmrdre) by [Alper Ebicoglu](https://twitter.com/alperebicoglu). |
|||
* [Converting Create/Edit Modal to Page - Blazor](https://community.abp.io/posts/converting-createedit-modal-to-page-blazor-eexdex8y) by [Enis Necipoglu](https://twitter.com/EnisNecipoglu). |
|||
* [Using Dapper with the ABP Framework](https://community.abp.io/posts/using-dapper-with-the-abp-framework-shp74p2l) by [Halil Ibrahim Kalkan](https://twitter.com/hibrahimkalkan). |
|||
* [ABP React Template](https://community.abp.io/posts/abp-react-template-33pjmran) by [Anto Subash](https://twitter.com/antosubash). |
|||
* [How to Export Data to Excel Files with ASP.NET Core Minimal API](https://community.abp.io/posts/how-to-export-data-to-excel-files-with-asp.net-core-minimal-api-79o45u3s) by [Berkan Sasmaz](https://twitter.com/berkansasmazz). |
|||
|
|||
Thanks to the ABP Community for all the content they have published. You can also [post your ABP-related (text or video) content](https://community.abp.io/articles/submit) to the ABP Community. |
|||
|
|||
### New ABP Blog Posts |
|||
|
|||
There are also some exciting blog posts written by the ABP team. You can see the following list for some of those articles: |
|||
|
|||
* [ABP Framework: Open Source Web Application Development Framework](https://blog.abp.io/abp/open-source-web-application-development-framework) by [Alper Ebicoglu](https://twitter.com/alperebicoglu). |
|||
* [ABP Framework: The Ultimate .NET Web Framework for Rapid Application Development](https://blog.abp.io/abp/ultimate-net-web-framework-for-rapid-application-development) by [Alper Ebicoglu](https://twitter.com/alperebicoglu). |
|||
* [Top 10 .NET Core Libraries Every Developer Should Know 🔥](https://blog.abp.io/abp/Top-10-.NET-Core-Libraries-Every-Developer-Should-Know) by [Alper Ebicoglu](https://twitter.com/alperebicoglu) |
|||
|
|||
## Conclusion |
|||
|
|||
This version comes with some new features and a lot of enhancements to the existing features. You can see the [Road Map](https://docs.abp.io/en/abp/7.2/Road-Map) documentation to learn about the release schedule and planned features for the next releases. Please try ABP v7.2 RC and provide feedback to help us release a more stable version. |
|||
|
|||
Thanks for being a part of this community! |
|||
|
After Width: | Height: | Size: 329 KiB |
|
After Width: | Height: | Size: 1.3 MiB |
|
After Width: | Height: | Size: 234 KiB |
|
After Width: | Height: | Size: 34 KiB |
|
After Width: | Height: | Size: 74 KiB |
|
After Width: | Height: | Size: 29 KiB |
|
After Width: | Height: | Size: 150 KiB |
|
After Width: | Height: | Size: 48 KiB |
@ -0,0 +1,118 @@ |
|||
# 💻 How to Optimize Your ASP.NET Application for Improved Performance 🚀 |
|||
|
|||
If you want your ASP.NET application to perform well, you need to optimize it for speed, responsiveness, and user experience. Performance optimization is critical for factors like fast page load times, improved response efficiency, and happy users. In this article, I'll provide several tips and tricks to help you optimize performance in ASP.NET Core. |
|||
|
|||
## 🚀 Use Response Compression in Your ASP.NET Application |
|||
You can use ASP.NET Core's built-in response compression middleware to compress the response data and reduce the amount of data that needs to be transferred over the network. To use response compression, add the following code to your application's Startup.cs file: |
|||
|
|||
```csharp |
|||
services.AddResponseCompression(options => |
|||
{ |
|||
options.EnableForHttps = true; |
|||
}); |
|||
|
|||
app.UseResponseCompression(); |
|||
``` |
|||
|
|||
## 🖼️ Optimize Images in Your ASP.NET Application: |
|||
|
|||
Images can be a major contributor to page bloat and slow load times. Here are some tips to optimize images: |
|||
|
|||
🖌️ Use a tool like ImageOptim or Kraken.io to compress and optimize images. |
|||
|
|||
🖼️ Specify the width and height of images in HTML so the browser can allocate space for them before they load. |
|||
|
|||
📝 Use alt attributes to provide descriptive text for images, which can improve accessibility and also help with SEO. |
|||
|
|||
📜 Use lazy loading for images that are below the fold, meaning they're not visible on the initial screen view. You can use libraries like Vanilla LazyLoad to implement lazy loading. |
|||
|
|||
📱 Use responsive images to serve different image sizes to different devices. This can improve page load times by reducing the size of images that are displayed on smaller devices. |
|||
|
|||
💻 Example: |
|||
|
|||
```html |
|||
<picture> |
|||
<source media="(min-width: 650px)" data-srcset="image.webp"> |
|||
<source media="(min-width: 465px)" data-srcset="image_small.webp"> |
|||
<img src="placeholder.png" data-src="image.webp" alt="Image" width="100" height="100" class="lazy" /> |
|||
</picture> |
|||
``` |
|||
|
|||
```javascript |
|||
var lazyLoadInstance = new LazyLoad(); |
|||
``` |
|||
|
|||
## 🧱 Optimize HTML in Your ASP.NET Application: |
|||
|
|||
The structure and organization of HTML can affect the page speed. Here are some tips to optimize HTML: |
|||
|
|||
📝 Use the heading tags (h1, h2, h3, etc.) in a logical and sequential order. |
|||
|
|||
🔩 Use the "defer" attribute for script tags that don't need to be executed immediately. This can improve the page load times by delaying the execution of scripts until after the page has rendered. |
|||
|
|||
🔩 Use the "async" attribute for script tags that can be executed asynchronously. This can further improve the page load times by allowing scripts to be downloaded and executed simultaneously. |
|||
|
|||
🧱 Use semantic HTML elements (like nav, section, and article) to provide additional structure and meaning to the page. |
|||
|
|||
## 🎨 Optimize CSS and JavaScript in Your ASP.NET Application: |
|||
|
|||
CSS and JavaScript files can be a major contributor to the page load times. Here are some tips to optimize CSS and JavaScript in your ASP.NET application: |
|||
|
|||
🔨 Minify and concatenate CSS and JavaScript files to reduce their size. |
|||
|
|||
🔩 Use the "defer" or "async" attributes for script tags to delay or asynchronously load scripts. |
|||
|
|||
## 🔡 Use system fonts in Your ASP.NET Application: |
|||
|
|||
Loading custom fonts can be slow and increase page load times. Using system fonts can improve page speed by allowing the browser to use fonts that are already installed on the user's device. |
|||
|
|||
## 🖼️ Use Placeholders and Progress Indicators in Your ASP.NET Application: |
|||
|
|||
To improve the perceived performance of your website, you can use placeholders and progress indicators for slow-loading sections of your page. You can use JavaScript to load these sections after the initial page load. |
|||
|
|||
💻 Example: |
|||
|
|||
```html |
|||
|
|||
<div id="placeholder" data-url="/slow-loading-content"> |
|||
<p>Loading...</p> |
|||
</div> |
|||
``` |
|||
|
|||
```javascript |
|||
const placeholder = document.querySelector('#placeholder'); |
|||
fetch(placeholder.dataset.url) |
|||
.then(response => response.text()) |
|||
.then(html => placeholder.innerHTML = html); |
|||
``` |
|||
|
|||
## 🔗 Use the Appropriate Link Text and ARIA Labels: |
|||
|
|||
When using links, use appropriate link texts that accurately describe the content of the linked page. This can improve the accessibility and also help with SEO. |
|||
|
|||
ARIA labels should also be used to provide additional context for links. This can also improve the accessibility and help with SEO. |
|||
|
|||
💻 Example: |
|||
|
|||
```html |
|||
<a href="https://example.com/" aria-label="Go to Example">Example</a> |
|||
<a href="https://example.com/" aria-label="Go to Another Example">Another Example</a> |
|||
``` |
|||
|
|||
## 🌐 Optimize the Third-party Resources in Your ASP.NET Application: |
|||
|
|||
Third-party resources like social media widgets and advertising scripts can slow down the page load times. Here are some tips to optimize third-party resources: |
|||
|
|||
🔩 Use asynchronous scripts when possible. |
|||
|
|||
🔍 Only load third-party resources that are necessary for the page. |
|||
|
|||
By following these optimization techniques, you can significantly improve the page speed of your ASP.NET Core web application. |
|||
|
|||
## What is ABP Framework? |
|||
|
|||
ABP Framework offers an opinionated architecture to build enterprise software solutions with ASP.NET Core best practices on top of the .NET and the ASP.NET Core platforms. It provides the fundamental web application infrastructure, production-ready dotnet startup templates, modules, asp.net core ui themes, tooling, guides and documentation to implement that ASP.NET core architecture properly and automate the details and repetitive work as much as possible. |
|||
|
|||
If you are starting a new ASP.NET Core project, try [abp.io](https://abp.io/) now... |
|||
|
|||
**IT IS FREE AND OPEN-SOURCE!** |
|||
@ -0,0 +1,86 @@ |
|||
# ABP.IO Platform 7.2 Final Has Been Released! |
|||
|
|||
[ABP Framework](https://abp.io/) and [ABP Commercial](https://commercial.abp.io/) 7.2 versions have been released today. |
|||
|
|||
## What's New With Version 7.2? |
|||
|
|||
All the new features were already explained in detail in the [7.2 RC Announcement Post](https://blog.abp.io/abp/ABP.IO-Platform-7.2-RC-Has-Been-Published), so no need to go over them again. Check it out for more details. |
|||
|
|||
## Getting Started with 7.2 |
|||
|
|||
### Creating New Solutions |
|||
|
|||
You can create a new solution with the ABP Framework version 7.2 by either using the `abp new` command or generating the CLI command on the [get started page](https://abp.io/get-started). |
|||
|
|||
> See the [getting started document](https://docs.abp.io/en/abp/latest/Getting-Started) for more. |
|||
|
|||
### How to Upgrade an Existing Solution |
|||
|
|||
#### Install/Update the ABP CLI |
|||
|
|||
First of all, install the ABP CLI or upgrade it to the latest version. |
|||
|
|||
If you haven't installed it yet: |
|||
|
|||
```bash |
|||
dotnet tool install -g Volo.Abp.Cli |
|||
``` |
|||
|
|||
To update the existing CLI: |
|||
|
|||
```bash |
|||
dotnet tool update -g Volo.Abp.Cli |
|||
``` |
|||
|
|||
#### Upgrading Existing Solutions with the ABP Update Command |
|||
|
|||
[ABP CLI](https://docs.abp.io/en/abp/latest/CLI) provides a handy command to update all the ABP related NuGet and NPM packages in your solution with a single command: |
|||
|
|||
```bash |
|||
abp update |
|||
``` |
|||
|
|||
Run this command in the root folder of your solution. |
|||
|
|||
## Migration Guides |
|||
|
|||
There are breaking changes in this version that may affect your application. |
|||
Please see the following migration documents, if you are upgrading from v7.1: |
|||
|
|||
* [ABP Framework 7.1 to 7.2 Migration Guide](https://docs.abp.io/en/abp/7.2/Migration-Guides/Abp-7_2) |
|||
* [ABP Commercial 7.1 to 7.2 Migration Guide](https://docs.abp.io/en/commercial/7.2/migration-guides/v7_2) |
|||
|
|||
## Community News |
|||
|
|||
### ABP - DOTNET CONF'23 |
|||
|
|||
 |
|||
|
|||
As the ABP team, we've organized 10+ [online events](https://community.abp.io/events) and gained a good experience with software talks. We are organizing ABP Dotnet Conference 2023, a full-featured software conference, on May 10. You can visit [https://abp.io/conference](https://abp.io/conference) to see the speakers, talks, schedules, and other details. |
|||
|
|||
Don't forget to take your seat and buy a ticket from [https://kommunity.com/volosoft/events/1st-abp-conference-96db1a54](https://kommunity.com/volosoft/events/1st-abp-conference-96db1a54)! |
|||
|
|||
### New ABP Community Posts |
|||
|
|||
There are exciting articles contributed by the ABP community as always. I will highlight some of them here: |
|||
|
|||
* [Converting Create/Edit Modal to Page AngularUI](https://community.abp.io/posts/converting-createedit-modal-to-page-angularui-doadhgil) by [Masum Ulu](https://twitter.com/masumulu) |
|||
* [How to Export Data to Excel Files with ASP.NET Core Minimal API](https://community.abp.io/posts/how-to-export-data-to-excel-files-with-asp.net-core-minimal-api-79o45u3s) by [Berkan Sasmaz](https://twitter.com/berkansasmazz) |
|||
* [ABP React Template](https://community.abp.io/posts/abp-react-template-33pjmran) by [Anto Subash](https://twitter.com/antosubash) |
|||
* [Using Dapper with the ABP Framework](https://community.abp.io/posts/using-dapper-with-the-abp-framework-shp74p2l) by [Halil Ibrahim Kalkan](https://twitter.com/hibrahimkalkan) |
|||
* [Converting Create/Edit Modal to Page - Blazor](https://community.abp.io/posts/converting-createedit-modal-to-page-blazor-eexdex8y) by [Enis Necipoglu](https://twitter.com/EnisNecipoglu) |
|||
* [What’s New in .NET 8 🧐 ? Discover ALL .NET 8 Features](https://community.abp.io/posts/whats-new-in-.net-8-discover-all-.net-8-features-llcmrdre) by [Alper Ebicoglu](https://twitter.com/alperebicoglu) |
|||
|
|||
Thanks to the ABP Community for all the content they have published. You can also [post your ABP-related (text or video) content](https://community.abp.io/articles/submit) to the ABP Community. |
|||
|
|||
### New ABP Blog Posts |
|||
|
|||
There are also some exciting blog posts written by the ABP team. You can see the following list for some of those articles: |
|||
|
|||
* [You Are Invited to ABP .NET Conf’23! 📣](https://blog.abp.io/abp/You-Are-Invited-to-ABP-dotNET-Conf23) by [Bige Beşikçi](https://twitter.com/bigedediki) |
|||
* [💻 Speed Up Your ASP.NET Application 🚀](https://blog.abp.io/abp/Speed-Up-Your-ASP.NET-Application) by [Salih Özkara](https://twitter.com/salihozkara_) |
|||
* [C# 12 🔍 Discover the Exciting New Features & Improvements 🆕🚀](https://blog.abp.io/abp/CSharp-12-Discover-the-Exciting-New-Features-and-Improvements) by [Alper Ebiçoğlu](https://twitter.com/alperebicoglu) |
|||
|
|||
## About the Next Version |
|||
|
|||
The next feature version will be 7.3. You can follow the [release planning here](https://github.com/abpframework/abp/milestones). Please [submit an issue](https://github.com/abpframework/abp/issues/new) if you have any problems with this version. |
|||
|
After Width: | Height: | Size: 329 KiB |
|
After Width: | Height: | Size: 234 KiB |
@ -0,0 +1,325 @@ |
|||
# Convert Create/Edit Modals to Page |
|||
|
|||
In this document we will explain how to convert the BookStore's Books create & edit modals to regular Angular component pages. |
|||
|
|||
## Before |
|||
|
|||
 |
|||
|
|||
## After |
|||
|
|||
 |
|||
|
|||
# BooksComponent |
|||
|
|||
This is the main component of the books management. The create & update operations are done in this page. So we'll remove the create & update operations from this page and move a separate angular component for each operation. Each component will be a page. |
|||
|
|||
- Remove the Create & Update modal on template |
|||
|
|||
 |
|||
|
|||
- Modify the **NewBook** button with a link to the **CreateBookComponent** page. |
|||
|
|||
```html |
|||
<button |
|||
*abpPermission="'BookStore.Books.Create'" |
|||
id="create" |
|||
class="btn btn-primary" |
|||
type="button" |
|||
[routerLink]="['create']" |
|||
> |
|||
<i class="fa fa-plus me-1"></i> |
|||
<span>{{ '::NewBook' | abpLocalization }}</span> |
|||
</button> |
|||
``` |
|||
|
|||
- Modify the **Edit** button with a link to the **EditBookComponent** page. |
|||
|
|||
```html |
|||
<button |
|||
*abpPermission="'BookStore.Books.Edit'" |
|||
ngbDropdownItem |
|||
[routerLink]="['edit', row.id]" |
|||
> |
|||
{{ '::Edit' | abpLocalization }} |
|||
</button> |
|||
``` |
|||
|
|||
- Remove all unused methods and variables in the `BookComponent` except the **book** variable, the **ngOnInit** and **delete** methods. |
|||
|
|||
|
|||
 |
|||
|
|||
- Also we can clear unncessary imports |
|||
|
|||
 |
|||
|
|||
|
|||
|
|||
# CreateBookComponent Page |
|||
|
|||
Create a new component by the name `create-book` in your project. |
|||
```bash |
|||
yarn ng g c book/create-book --skip-tests --style=none |
|||
``` |
|||
|
|||
- `create-book.component.html` |
|||
|
|||
```html |
|||
<div class="card"> |
|||
<div class="card-body"> |
|||
<form [formGroup]="form" (ngSubmit)="save()"> |
|||
<div class="form-group"> |
|||
<label for="author-id">Author</label><span> * </span> |
|||
<select class="form-control" id="author-id" formControlName="authorId"> |
|||
<option [ngValue]="null">Select author</option> |
|||
<option [ngValue]="author.id" *ngFor="let author of authors$ | async"> |
|||
{{ author.name }} |
|||
</option> |
|||
</select> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label for="book-name">Name</label><span> * </span> |
|||
<input type="text" id="book-name" class="form-control" formControlName="name" autofocus /> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label for="book-price">Price</label><span> * </span> |
|||
<input type="number" id="book-price" class="form-control" formControlName="price" /> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label for="book-type">Type</label><span> * </span> |
|||
<select class="form-control" id="book-type" formControlName="type"> |
|||
<option [ngValue]="null">Select a book type</option> |
|||
<option [ngValue]="type.value" *ngFor="let type of bookTypes"> |
|||
{{ '::Enum:BookType.' + type.value | abpLocalization }} |
|||
</option> |
|||
</select> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label>Publish date</label><span> * </span> |
|||
<input |
|||
#datepicker="ngbDatepicker" |
|||
class="form-control" |
|||
name="datepicker" |
|||
formControlName="publishDate" |
|||
ngbDatepicker |
|||
(click)="datepicker.toggle()" |
|||
/> |
|||
</div> |
|||
|
|||
<div class="pt-2"> |
|||
<button type="button" class="btn btn-secondary m-1" [routerLink]="['/books']"> |
|||
{{ '::Cancel' | abpLocalization }} |
|||
</button> |
|||
|
|||
<button class="btn btn-primary"> |
|||
<i class="fa fa-check mr-1"></i> |
|||
{{ '::Save' | abpLocalization }} |
|||
</button> |
|||
</div> |
|||
</form> |
|||
</div> |
|||
</div> |
|||
``` |
|||
|
|||
- `create-book.component.ts` |
|||
|
|||
```ts |
|||
import { Component, inject } from '@angular/core'; |
|||
import { Router } from '@angular/router'; |
|||
import { FormBuilder, FormGroup, Validators } from '@angular/forms'; |
|||
import { map } from 'rxjs'; |
|||
import { NgbDateNativeAdapter, NgbDateAdapter } from '@ng-bootstrap/ng-bootstrap'; |
|||
import { BookService, bookTypeOptions } from '@proxy/books'; |
|||
|
|||
const { required } = Validators; |
|||
|
|||
@Component({ |
|||
selector: 'app-create-book', |
|||
templateUrl: './create-book.component.html', |
|||
providers: [{ provide: NgbDateAdapter, useClass: NgbDateNativeAdapter }], |
|||
}) |
|||
export class CreateBookComponent { |
|||
//inject() function came with Angular v14, detail: https://angular.io/api/core/inject |
|||
private readonly router = inject(Router); |
|||
private readonly fb = inject(FormBuilder); |
|||
private readonly bookService = inject(BookService); |
|||
|
|||
form: FormGroup; |
|||
authors$ = this.bookService.getAuthorLookup().pipe(map(({ items }) => items)); |
|||
bookTypes = bookTypeOptions; |
|||
|
|||
private buildForm() { |
|||
this.form = this.fb.group({ |
|||
authorId: [null, required], |
|||
name: [null, required], |
|||
type: [null, required], |
|||
publishDate: [undefined, required], |
|||
price: [null, required], |
|||
}); |
|||
} |
|||
|
|||
constructor() { |
|||
this.buildForm(); |
|||
} |
|||
|
|||
save() { |
|||
if (this.form.invalid) return; |
|||
|
|||
this.bookService.create(this.form.value).subscribe(() => { |
|||
this.router.navigate(['/books']); |
|||
}); |
|||
} |
|||
} |
|||
``` |
|||
|
|||
# EditBookComponent Page |
|||
|
|||
Create a new component by the name **edit-book** in your project. |
|||
|
|||
```bash |
|||
yarn ng g c book/edit-book --skip-tests --style=none |
|||
``` |
|||
|
|||
- `edit-book.component.html` |
|||
|
|||
```html |
|||
<div class="card"> |
|||
<div class="card-body"> |
|||
<form *ngIf="form" [formGroup]="form" (ngSubmit)="save()"> |
|||
<div class="form-group"> |
|||
<label for="author-id">Author</label><span> * </span> |
|||
<select class="form-control" id="author-id" formControlName="authorId"> |
|||
<option [ngValue]="null">Select author</option> |
|||
<option [ngValue]="author.id" *ngFor="let author of authors$ | async"> |
|||
{{ author.name }} |
|||
</option> |
|||
</select> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label for="book-name">Name</label><span> * </span> |
|||
<input type="text" id="book-name" class="form-control" formControlName="name" autofocus /> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label for="book-price">Price</label><span> * </span> |
|||
<input type="number" id="book-price" class="form-control" formControlName="price" /> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label for="book-type">Type</label><span> * </span> |
|||
<select class="form-control" id="book-type" formControlName="type"> |
|||
<option [ngValue]="null">Select a book type</option> |
|||
<option [ngValue]="type.value" *ngFor="let type of bookTypes"> |
|||
{{ '::Enum:BookType.' + type.value | abpLocalization }} |
|||
</option> |
|||
</select> |
|||
</div> |
|||
|
|||
<div class="mt-2"> |
|||
<label>Publish date</label><span> * </span> |
|||
<input |
|||
#datepicker="ngbDatepicker" |
|||
class="form-control" |
|||
name="datepicker" |
|||
formControlName="publishDate" |
|||
ngbDatepicker |
|||
(click)="datepicker.toggle()" |
|||
/> |
|||
</div> |
|||
|
|||
<div class="pt-2"> |
|||
<button type="button" class="btn btn-secondary m-1" [routerLink]="['/books']"> |
|||
{{ '::Cancel' | abpLocalization }} |
|||
</button> |
|||
|
|||
<button class="btn btn-primary"> |
|||
<i class="fa fa-check mr-1"></i> |
|||
{{ '::Save' | abpLocalization }} |
|||
</button> |
|||
</div> |
|||
</form> |
|||
</div> |
|||
</div> |
|||
``` |
|||
|
|||
- `edit-book.component.ts` |
|||
|
|||
```ts |
|||
import { Component, inject } from '@angular/core'; |
|||
import { ActivatedRoute, Router } from '@angular/router'; |
|||
import { FormBuilder, FormGroup, Validators } from '@angular/forms'; |
|||
import { filter, map, switchMap, tap } from 'rxjs'; |
|||
import { NgbDateNativeAdapter, NgbDateAdapter } from '@ng-bootstrap/ng-bootstrap'; |
|||
import { BookDto, BookService, bookTypeOptions } from '@proxy/books'; |
|||
|
|||
const { required } = Validators; |
|||
|
|||
@Component({ |
|||
selector: 'app-edit-book', |
|||
templateUrl: './edit-book.component.html', |
|||
providers: [{ provide: NgbDateAdapter, useClass: NgbDateNativeAdapter }], |
|||
}) |
|||
export class EditBookComponent { |
|||
//inject() function came with Angular v14, detail: https://angular.io/api/core/inject |
|||
private readonly router = inject(Router); |
|||
private readonly activatedRoute = inject(ActivatedRoute); |
|||
private readonly fb = inject(FormBuilder); |
|||
private readonly bookService = inject(BookService); |
|||
|
|||
id: string; |
|||
form: FormGroup; |
|||
authors$ = this.bookService.getAuthorLookup().pipe(map(({ items }) => items)); |
|||
bookTypes = bookTypeOptions; |
|||
|
|||
private buildForm(book: BookDto): void { |
|||
this.form = this.fb.group({ |
|||
authorId: [book.authorId, required], |
|||
name: [book.name, required], |
|||
type: [book.type, required], |
|||
publishDate: [new Date(book.publishDate), required], |
|||
price: [book.price, required], |
|||
}); |
|||
} |
|||
|
|||
constructor() { |
|||
this.activatedRoute.params |
|||
.pipe( |
|||
filter(params => params.id), |
|||
tap(({ id }) => (this.id = id)), |
|||
switchMap(({ id }) => this.bookService.get(id)), |
|||
tap(book => this.buildForm(book)) |
|||
) |
|||
.subscribe(); |
|||
} |
|||
|
|||
save(): void { |
|||
if (this.form.invalid) return; |
|||
|
|||
this.bookService.update(this.id, this.form.value).subscribe(() => { |
|||
this.router.navigate(['/books']); |
|||
}); |
|||
} |
|||
} |
|||
``` |
|||
|
|||
# Update BookRoutingModule |
|||
Finally add 2 items to the routes array in the `book-routing.module.ts` |
|||
```ts |
|||
import { CreateBookComponent } from './create-book/create-book.component'; |
|||
import { EditBookComponent } from './edit-book/edit-book.component'; |
|||
|
|||
const routes: Routes = [ |
|||
{ path: '', component: BookComponent, canActivate: [AuthGuard, PermissionGuard] }, |
|||
{ path: 'create', component: CreateBookComponent }, |
|||
{ path: 'edit/:id', component: EditBookComponent }, |
|||
]; |
|||
``` |
|||
|
|||
|
|||
You can check the following commit for more details: https://github.com/abpframework/abp-samples/commit/351ad5e093036702edbb15169968935496afea0e |
|||
|
After Width: | Height: | Size: 23 KiB |
|
After Width: | Height: | Size: 31 KiB |
|
After Width: | Height: | Size: 129 KiB |
|
After Width: | Height: | Size: 291 KiB |
|
After Width: | Height: | Size: 678 KiB |
@ -0,0 +1,36 @@ |
|||
# Authority Delegation in ABP Commercial |
|||
|
|||
In this post, I'll explain a new feature that comes with the ABP Commercial `v7.2.0`. It's called **Authority Delegation**. |
|||
|
|||
## Authority Delegation |
|||
|
|||
Authority Delegation is a way of delegating the responsibility of the current user to a different user(s) for a limited time. Thus, the user can switch to the delegated user's account and perform actions on their behalf. |
|||
|
|||
> This feature is part of the [Account Pro module](https://commercial.abp.io/modules/Volo.Account.Pro), which is one of the application PRO modules of [ABP Commercial](https://commercial.abp.io/). |
|||
|
|||
### Delegating a new user |
|||
|
|||
After logging into the application, you can see the `Authority Delegation` menu item under the user menu. When you click the menu, a modal will open, and in the first tab of the modal, you will see the list of delegated users. |
|||
|
|||
 |
|||
|
|||
You can click the `Delegate New User` button to delegate a new user: |
|||
|
|||
 |
|||
|
|||
* You can specify a time range to ensure the delegation is only available within the time range. |
|||
* You can make multiple delegates to the same user and set different delegate time ranges. |
|||
|
|||
> The delegation has three states: `Expired`, `Active`, and `Future`. These states are set automatically by checking the specified time interval. |
|||
|
|||
### My delegated users |
|||
|
|||
A list of users who delegated me to log in on behalf of them can be seen in the figure: |
|||
|
|||
 |
|||
|
|||
You can click the `Login` button to log in to the application as a delegated user and go back to your account by clicking the `Back to my account` icon. |
|||
|
|||
 |
|||
|
|||
> The **Authority Delegation** feature uses the [impersonation system](https://docs.abp.io/en/commercial/latest/modules/account/impersonation) internally. |
|||
|
After Width: | Height: | Size: 184 KiB |
|
After Width: | Height: | Size: 335 KiB |
|
After Width: | Height: | Size: 255 KiB |
|
After Width: | Height: | Size: 245 KiB |
@ -0,0 +1,51 @@ |
|||
# Checkbox Component |
|||
|
|||
The ABP Checkbox Component is a reusable form input component for the checkbox type. |
|||
|
|||
# Inputs |
|||
|
|||
- `label` |
|||
- `labelClass (default form-check-label)` |
|||
- `checkboxId` |
|||
- `checkboxReadonly` |
|||
- `checkboxReadonly (default form-check-input)` |
|||
- `checkboxStyle` |
|||
|
|||
# Outputs |
|||
|
|||
- `checkboxBlur` |
|||
- `checkboxFocus` |
|||
|
|||
# Usage |
|||
|
|||
The ABP Checkbox component is a part of the `ThemeSharedModule` module. If you've imported that module into your module, there's no need to import it again. If not, then first import it as shown below: |
|||
|
|||
```ts |
|||
// my-feature.module.ts |
|||
|
|||
import { ThemeSharedModule } from "@abp/ng.theme.shared"; |
|||
import { CheckboxDemoComponent } from "./CheckboxDemoComponent.component"; |
|||
|
|||
@NgModule({ |
|||
imports: [ |
|||
ThemeSharedModule, |
|||
// ... |
|||
], |
|||
declarations: [CheckboxDemoComponent], |
|||
// ... |
|||
}) |
|||
export class MyFeatureModule {} |
|||
``` |
|||
|
|||
Then, the `abp-checkbox` component can be used. See the example below: |
|||
|
|||
```html |
|||
<div class="form-check"> |
|||
<abp-checkbox label="Yes,I Agree" checkboxId="checkbox-input"> |
|||
</abp-checkbox> |
|||
</div> |
|||
``` |
|||
|
|||
See the checkbox input result below: |
|||
|
|||
 |
|||
@ -0,0 +1,49 @@ |
|||
# Form Input Component |
|||
|
|||
The ABP FormInput Component is a reusable form input component for the text type. |
|||
|
|||
# Inputs |
|||
* `label` |
|||
* `labelClass (default form-label)` |
|||
* `inputPlaceholder` |
|||
* `inputReadonly` |
|||
* `inputClass (default form-control)` |
|||
|
|||
# Outputs |
|||
* `formBlur` |
|||
* `formFocus` |
|||
|
|||
# Usage |
|||
|
|||
The ABP FormInput component is a part of the `ThemeSharedModule` module. If you've imported that module into your module, there's no need to import it again. If not, then first import it as shown below: |
|||
|
|||
```ts |
|||
import { ThemeSharedModule } from "@abp/ng.theme.shared"; |
|||
import { FormInputDemoComponent } from "./FomrInputDemoComponent.component"; |
|||
|
|||
@NgModule({ |
|||
imports: [ |
|||
ThemeSharedModule, |
|||
// ... |
|||
], |
|||
declarations: [FormInputDemoComponent], |
|||
}) |
|||
export class MyFeatureModule {} |
|||
``` |
|||
|
|||
Then, the `abp-form-input` component can be used. See the example below: |
|||
|
|||
```html |
|||
<div class="row"> |
|||
<div class="col-4"> |
|||
<abp-form-input |
|||
label="AbpAccount::UserNameOrEmailAddress" |
|||
inputId="login-input-user-name-or-email-address" |
|||
></abp-form-input> |
|||
</div> |
|||
</div> |
|||
``` |
|||
|
|||
See the form input result below: |
|||
|
|||
 |
|||
|
After Width: | Height: | Size: 2.7 KiB |
|
After Width: | Height: | Size: 5.8 KiB |
@ -0,0 +1,45 @@ |
|||
# Security Headers |
|||
|
|||
ABP Framework allows you to add frequently used security headers into your application. The following security headers will be added as response headers to your application if you use the `UseAbpSecurityHeaders` middleware: |
|||
|
|||
* `X-Content-Type-Options`: Tells the browser to not try and guess what a mime-type of a resource might be, and to just take what mime-type the server has returned. |
|||
* `X-XSS-Protection`: This is a feature of Internet Explorer, Chrome, and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks. |
|||
* `X-Frame-Options`: This header can be used to indicate whether or not a browser should be allowed to render a page in a `<iframe>` tag. By specifying this header value as *SAMEORIGIN*, you can make it displayed in a frame on the same origin as the page itself. |
|||
* `Content-Security-Policy`: This response header allows you to restrict which resources (such as JavaScript, CSS, images, manifests, etc.) can be loaded, and the URLs that they can be loaded from. This security header will only be added if you configure the `AbpSecurityHeadersOptions` class and enable it. |
|||
|
|||
## Configuration |
|||
|
|||
### AbpSecurityHeadersOptions |
|||
|
|||
`AbpSecurityHeadersOptions` is the main class to enable the `Content-Security-Policy` header, define its value and set other security headers that you want to add to your application. |
|||
|
|||
**Example:** |
|||
|
|||
```csharp |
|||
Configure<AbpSecurityHeadersOptions>(options => |
|||
{ |
|||
options.UseContentSecurityPolicyHeader = true; //false by default |
|||
options.ContentSecurityPolicyValue = "object-src 'none'; form-action 'self'; frame-ancestors 'none'"; |
|||
|
|||
//adding additional security headers |
|||
options.Headers["Referrer-Policy"] = "no-referrer"; |
|||
}); |
|||
``` |
|||
|
|||
> If the header is the same, the additional security headers you defined take precedence over the default security headers. In other words, it overrides the default security headers' values. |
|||
|
|||
## Security Headers Middleware |
|||
|
|||
Security Headers middleware is an ASP.NET Core request pipeline [middleware](https://docs.microsoft.com/en-us/aspnet/core/fundamentals/middleware) that adds pre-defined security headers to your application, including `X-Content-Type-Options`, `X-XSS-Protection`, and `X-Frame-Options`. Additionally, this middleware also includes those unique security headers in your application if you configure the `AbpSecurityHeadersOptions` as mentioned above. |
|||
|
|||
**Example:** |
|||
|
|||
```csharp |
|||
app.UseAbpSecurityHeaders(); |
|||
``` |
|||
|
|||
> You can add this middleware into the `OnApplicationInitialization` method of your module class to register it to the request pipeline. This middleware is already configured in the [ABP Commercial Startup Templates](https://docs.abp.io/en/commercial/latest/startup-templates/index), so you don't need to manually add it if you are using one of these startup templates. |
|||
|
|||
After that, you have registered the `UseAbpSecurityHeaders` middleware into the request pipeline, the defined security headers will be shown in the response headers as in the figure below: |
|||
|
|||
 |
|||
|
After Width: | Height: | Size: 25 KiB |
|
After Width: | Height: | Size: 12 KiB |
@ -0,0 +1,78 @@ |
|||
using System; |
|||
using System.Net.Mime; |
|||
using System.Text; |
|||
using Microsoft.AspNetCore.Http; |
|||
using Microsoft.Net.Http.Headers; |
|||
|
|||
namespace Microsoft.AspNetCore.Internal; |
|||
|
|||
/// <summary>
|
|||
/// https://github.com/dotnet/aspnetcore/blob/release/7.0/src/Shared/ResponseContentTypeHelper.cs
|
|||
/// </summary>
|
|||
public static class ResponseContentTypeHelper |
|||
{ |
|||
/// <summary>
|
|||
/// Gets the content type and encoding that need to be used for the response.
|
|||
/// The priority for selecting the content type is:
|
|||
/// 1. ContentType property set on the action result
|
|||
/// 2. <see cref="ContentType"/> property set on <see cref="HttpResponse"/>
|
|||
/// 3. Default content type set on the action result
|
|||
/// </summary>
|
|||
/// <remarks>
|
|||
/// The user supplied content type is not modified and is used as is. For example, if user
|
|||
/// sets the content type to be "text/plain" without any encoding, then the default content type's
|
|||
/// encoding is used to write the response and the ContentType header is set to be "text/plain" without any
|
|||
/// "charset" information.
|
|||
/// </remarks>
|
|||
public static void ResolveContentTypeAndEncoding( |
|||
string? actionResultContentType, |
|||
string? httpResponseContentType, |
|||
(string defaultContentType, Encoding defaultEncoding) @default, |
|||
Func<string, Encoding> getEncoding, |
|||
out string resolvedContentType, |
|||
out Encoding resolvedContentTypeEncoding) |
|||
{ |
|||
var (defaultContentType, defaultContentTypeEncoding) = @default; |
|||
|
|||
// 1. User sets the ContentType property on the action result
|
|||
if (actionResultContentType != null) |
|||
{ |
|||
resolvedContentType = actionResultContentType; |
|||
var actionResultEncoding = getEncoding(actionResultContentType); |
|||
resolvedContentTypeEncoding = actionResultEncoding ?? defaultContentTypeEncoding; |
|||
return; |
|||
} |
|||
|
|||
// 2. User sets the ContentType property on the http response directly
|
|||
if (!string.IsNullOrEmpty(httpResponseContentType)) |
|||
{ |
|||
var mediaTypeEncoding = getEncoding(httpResponseContentType); |
|||
if (mediaTypeEncoding != null) |
|||
{ |
|||
resolvedContentType = httpResponseContentType; |
|||
resolvedContentTypeEncoding = mediaTypeEncoding; |
|||
} |
|||
else |
|||
{ |
|||
resolvedContentType = httpResponseContentType; |
|||
resolvedContentTypeEncoding = defaultContentTypeEncoding; |
|||
} |
|||
|
|||
return; |
|||
} |
|||
|
|||
// 3. Fall-back to the default content type
|
|||
resolvedContentType = defaultContentType; |
|||
resolvedContentTypeEncoding = defaultContentTypeEncoding; |
|||
} |
|||
|
|||
public static Encoding GetEncoding(string mediaType) |
|||
{ |
|||
if (MediaTypeHeaderValue.TryParse(mediaType, out var parsed)) |
|||
{ |
|||
return parsed.Encoding; |
|||
} |
|||
|
|||
return default; |
|||
} |
|||
} |
|||
Some files were not shown because too many files changed in this diff
Loading…
Reference in new issue