Activities of "Bryan-EDV"

We are using angular + abp setup

Would there be any issues if we were to try using the module leveraging razor pages? or better to wait till 10.1 before implementing the FE screens? thanks

Hi Maliming,

Take a simplified flow:

1. User adds items to cart
2. Upon checkout, create one payment request with _paymentRequestAppService.CreateAsync
3. the payment request would have a list of products which correspond to the items in the cart
4. on each product, i add extra properties on the details of the product. e.g. course id, target user id
5. I listen to the Volo.Payment.PaymentRequestCompleted event
6. Handle event by adding user paymentRequest.Products[n].ExtraProperties.UserId to the relevant courses paymentRequest.Products[n].ExtraProperties.CourseId

Is this flow and my understanding correct?

Could you also advise what steps are needed if we are using ABP with Angular?

Many thanks

Sure, thanks.

For the other part of the qn,

In addition, I’m planning to implement the following workflow:

1. A customer browses available courses/modules.
2. They add selected items to a shopping cart.
3. They proceed to checkout and make payment.
4. Upon successful payment:
5. The customer is added to a join table (e.g., UserCourse or Enrollment).
6. This grants them access to the course(s) they purchased.

Could you advise on the best practices to implement this in ABP?

Oh i realised its a different account. Bryan-EDV is not Lexarius

Hi

Strangely can't see that screen.

just this one.

Also my user is Bryan-EDV here:

But when i click on my account, it is lexarius

i think Bryan-EDV was renamed to app-access@lexarius.com aka lexarius

Seems to be outdated

[maliming] said: hi

Can you share the output of the abp login-info command?

Thanks.

$ abp login-info
[09:59:39 INF] You are running the second generation of the ABP CLI. If you're interested in the legacy CLI, see https://abp.io/new-cli
📌 ABP CLI 0.9.26
📌 A newer version of the ABP CLI is available: 2.0.2
🔼 dotnet tool update -g Volo.Abp.Studio.Cli
[09:59:41 INF] 
Login info:
Name: Lexarius Limited
Surname: 
Username: lexarius
Email Address: app-access@lexarius.com
Organization: 

[sumeyye.kurtulus] said: Hi! Here's an approach you can follow:

const userNameField = new FormProp<IdentityUserDto>({ 
  type: ePropType.String, 
  name: 'userName', 
  displayName: 'New Username', 
  id: 'userName', 
  autocomplete: 'new-username', 
  validators: _ => [Validators.required, Validators.minLength(4)], 
}); 
 
export function userCreateFormContributor(formProps: FormPropList<IdentityUserDto>) { 
  const userNameIndex = formProps.indexOf('userName', (action, name) => action.name === name); 
  formProps.dropByIndex(userNameIndex); 
  formProps.addByIndex(userNameField, userNameIndex); 
} 
 
export const identityCreateFormContributors: IdentityCreateFormPropContributors = { 
  [eIdentityComponents.Users]: [userCreateFormContributor], 
}; 
 
export const identityEditFormContributors: IdentityEditFormPropContributors = { 
  [eIdentityComponents.Users]: [userCreateFormContributor], 
}; 

Then, configure your route like this:

// app-routing.module 
... 
{ 
  path: 'identity', 
  loadChildren: () => 
    import('@volo/abp.ng.identity').then(m => 
      m.IdentityModule.forLazy({ 
        createFormPropContributors: identityCreateFormContributors, 
        editFormPropContributors: identityCreateFormContributors, 
      }), 
    ), 
}, 
... 

Let me know if you need any further help!

ah, thank you works now. i had a similar code by the id was in PascalCase , therefore it wasn't working.

is it ok if i get my ticket allocation refunded for this please?

[AI-Bot] said: const usernameProp = propList.get('userName'); if (usernameProp) { // Update validators as needed usernameProp.validators = () => [ Validators.required, Validators.minLength(6), // Example: minimum length Validators.pattern(/^[a-zA-Z0-9_]+$/) // Example: alphanumeric and underscores only ];

validators is a read only property