fix(elements): Progressive sign up ticket flow by brkalow · Pull Request #4318 · clerk/javascript

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

brkalow · 2024-10-11T18:02:30Z

Description

Fixed a bug in the sign up flow where the sign up form was unable to accept additional requirements when initiated from a ticket.

fixes SDKI-697

Checklist

npm test runs as expected.
npm run build runs as expected.
(If applicable) JSDoc comments have been added or updated for any package exports
(If applicable) Documentation has been updated

Type of change

changeset-bot · 2024-10-11T18:02:33Z

🦋 Changeset detected

Latest commit: 8d3279e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@clerk/elements	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

brkalow · 2024-10-11T18:30:34Z

- target: 'Start',
- reenter: true,


This was causing the child machine to be re-created, and subsequently it would move right back to Attempting because of the presence of the ticket. For RESET.STEP specifically, we want to update the formRef of the child machine as this even is fired when the form machine is re-created.

There might be a better spot to put this that makes the intent more explicit. The underlying attempt actor was getting canceled, and subsequently re-created, by the reinitialization of the start machine. Changing this to only updating the form ref (which is what triggers RESET.STEP) solved the re-initialization issue.

brkalow · 2024-10-11T18:31:15Z

+ {
+ guard: and(['hasTicket', 'isMissingRequirements']),
+ target: 'Pending',
+ },


When the sign up attempt is missing requirements, users need to be able to submit the form, so we move to Pending

brkalow · 2024-10-11T18:51:53Z

 if (field) {
 field.checked = event.field.checked;
- field.disabled = event.field.disabled || false;
+ field.disabled = event.field.disabled ?? field.disabled;


I'm not sure if this matters in practice (field shouldn't get updated if disabled), but if this does happen, we want to retain the existing disabled value.

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Fix progressive sign up ticket flow
4766abc

adds changeset
3aa6b57

clerk-cookie added the elements label Oct 11, 2024

brkalow commented Oct 11, 2024
View reviewed changes

Align machine ID with other steps
8d3279e

brkalow commented Oct 11, 2024
View reviewed changes

brkalow requested review from dstaley, jacekradko and tmilewski October 11, 2024 18:52

tmilewski approved these changes Oct 11, 2024
View reviewed changes

dstaley approved these changes Oct 11, 2024
View reviewed changes

brkalow merged commit 7cff9d8 into mainOct 14, 2024

brkalow deleted the brk.fix/progressive-ticket branch October 14, 2024 20:30

clerk-cookie mentioned this pull request Oct 14, 2024
ci(repo): Version packages #4323
Merged

izaaklauer pushed a commit that referenced this pull request Oct 17, 2024
fix(elements): Progressive sign up ticket flow (#4318)
c23a2a9

wobsoriano pushed a commit that referenced this pull request Feb 8, 2025
fix(elements): Progressive sign up ticket flow (#4318)
964327a

Uh oh!

Conversation

brkalow commented Oct 11, 2024

Description

Checklist

Type of change

Uh oh!

changeset-botBot commented Oct 11, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

brkalow commented Oct 11, 2024

Description

Checklist

Type of change

Uh oh!

changeset-botBot commented Oct 11, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

brkalow commented Oct 11, 2024

Description

Checklist

Type of change

Uh oh!

changeset-botBot commented Oct 11, 2024• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🦋 Changeset detected

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

changeset-botBot commented Oct 11, 2024•
edited
Loading

changeset-botBot commented Oct 11, 2024•
edited
Loading

changeset-botBot commented Oct 11, 2024•
edited
Loading

changeset-botBot commented Oct 11, 2024•
edited
Loading