Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FIO-7507: Publish dev tag to npm #1060

Merged
merged 29 commits into from
May 21, 2024
Merged

Conversation

ryanformio
Copy link
Contributor

@ryanformio ryanformio commented Mar 20, 2024

Link to Jira Ticket

https://formio.atlassian.net/browse/FIO-7507

Description

What changed?

Added a publish job to push to a "dev" npm tag that includes a PR number and commit short hash as identifiers.

Comparison RC published code:
https://www.npmjs.com/package/@formio/angular/v/7.5.0-rc.1?activeTab=code

To compare aginst for DEV published code:
https://www.npmjs.com/package/@formio/angular/v/7.5.0-dev.1060.57ea833?activeTab=code

Why have you chosen this solution?

Retains a unique version for the commit and easily identifiable what commit the version belongs to.

Breaking Changes / Backwards Compatibility

n/a

Dependencies

n/a

How has this PR been tested?

https://github.com/formio/angular/actions/runs/8394115755

Checklist:

  • I have completed the above PR template
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (if applicable)
  • My changes generate no new warnings
  • My changes include tests that prove my fix is effective (or that my feature works as intended)
  • New and existing unit/integration tests pass locally with my changes
  • Any dependent changes have corresponding PRs that are listed above

@ryanformio ryanformio marked this pull request as ready for review March 22, 2024 17:24
@@ -17,7 +17,7 @@ export class FormioReportComponent extends FormioComponent implements OnInit, On
@Output() fetchDataError = new EventEmitter<any>();
@ViewChild('report', { static: true }) declare formioElement?: ElementRef<any>;

public isLoading: boolean;
// public isLoading: boolean; // Was not allowing yarn build
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not so certain about this change in the context of this ticket - I gather this causes a TypeScript error? If that's the case, how does this build ever succeed? This library is routinely built and published in our build pipelines

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overlooked before committing. Retested, looks like it is possibly redundant and can be removed.

image

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess my issue is that "possibly redundant" is not enough evidence for me to clobber a class instance variable in a PR that is just trying to publish a dev tag to npm. If we're not absolutely certain, let's check with the author of the code (Tanya?), who may say "you can just add an initializer to the class" or "sure go ahead it's not necessary"

Copy link
Contributor Author

@ryanformio ryanformio May 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FormioReportComponent extends FormioComponent which extends FormioBaseComponent which includes an isLoading property already, which I believe it where our redundancy is coming from.

FormioReportComponent (causes redundant error)

FormioBaseComponent

When running yarn build on commit where redundancy was added

image

@ryanformio ryanformio requested a review from brendanbond May 3, 2024 18:45
@brendanbond brendanbond merged commit 9e113e1 into master May 21, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants