<!-- 
RSS generated by JIRA (1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d) at Thu Feb 08 23:14:19 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary add field=key&field=summary to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>FOLIO Jira</title>
    <link>https://folio-org.atlassian.net</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>1001.0.0-SNAPSHOT</version>
        <build-number>100246</build-number>
        <build-date>07-02-2024</build-date>
    </build-info>

<item>
            <title>[FOLIO-1570] Identify release procedure for folio/react-big-calendar in CI</title>
                <link>https://folio-org.atlassian.net/browse/FOLIO-1570</link>
                <project id="10290" key="FOLIO">FOLIO</project>
                    <description>&lt;p&gt;It is currently not possible to include &lt;b&gt;&amp;#64;folio/react-big-calendar&lt;/b&gt; at the tip of master within a platform build without build errors.  This complicates release of &lt;b&gt;platform-complete&lt;/b&gt; or any other platform that includes &lt;b&gt;ui-calendar&lt;/b&gt;. &lt;/p&gt;

&lt;p&gt;As a fork of a project, it appears folio/react-big-calendar may require its own release procedure.  For example, master contains a babel config defining a plugin not present in our webpack config.  Looking at currently released artifacts on &lt;b&gt;npm-folio&lt;/b&gt;, these babel settings are not included.  This leads me to believe the project requires some pre-transpilation before publishing a release and including it within a FOLIO platform.&lt;/p&gt;

&lt;p&gt;Normally we include &lt;b&gt;&amp;#64;folio&lt;/b&gt;-scoped modules in the transpilation process since we author the source.  However, we do have &lt;a href=&quot;https://github.com/folio-org/stripes-core/blob/b08b32680a3b3bd2b7ab6beecd4394e097fea62e/webpack/babel-loader-rule.js#L3-L6&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;logic in our build process&lt;/a&gt; to exclude specific folio-scoped modules that should not be transpiled.&lt;/p&gt;

&lt;p&gt;My guess is folio/react-big-calendar should be added to this list.  However, we will need to know the proper process to publish this module to both &lt;b&gt;npm-folio&lt;/b&gt; and &lt;b&gt;npm-folioci&lt;/b&gt;.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Update:&lt;/b&gt;  &lt;/p&gt;

&lt;p&gt;As discussed during yesterday&apos;s (Oct.18) Stripes call, it was noted the upstream &lt;a href=&quot;https://github.com/intljusticemission/react-big-calendar/blob/master/package.json&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;react-big-calendar&lt;/a&gt; project has changes which would alleviate the current publishing issues.  Notably, the package.json&apos;s &quot;main&quot; entry points to the generated &quot;lib/index.js&quot; and the &quot;files&quot; array includes all of /lib.&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;&quot;main&quot;: &quot;lib/index.js&quot;,
&quot;files&quot;: [
  &quot;lib/&quot;,
  &quot;LICENSE&quot;,
  &quot;README.md&quot;,
  &quot;CHANGELOG.md&quot;
],
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Merging the latest would help with the current publishing issue, however, also introduces the need to review other upstream changes depending on how much our fork has diverged.&lt;/p&gt;</description>
                <environment></environment>
        <key id="80795">FOLIO-1570</key>
            <summary>Identify release procedure for folio/react-big-calendar in CI</summary>
                <type id="10003" iconUrl="https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium">Task</type>
                                            <priority id="10002" iconUrl="https://dev.folio.org/assets/jira-priority/jira-p3.svg">P3</priority>
                        <status id="6" iconUrl="https://folio-org.atlassian.net/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Done</resolution>
                                                        <assignee accountid="557058:624212b9-5938-4e3b-84c6-8c8a8db84996">Matthew Jones</assignee>
                                                                <reporter accountid="557058:624212b9-5938-4e3b-84c6-8c8a8db84996">Matthew Jones</reporter>
                                    <labels>
                    </labels>
                <created>Wed, 10 Oct 2018 21:03:36 +0000</created>
                <updated>Mon, 12 Nov 2018 14:25:11 +0000</updated>
                            <resolved>Mon, 22 Oct 2018 19:16:12 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                <comments>
                                                            <comment id="192705" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Wed, 10 Oct 2018 21:08:20 +0000"  >&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5e17508d5361330daaeb6d63&quot; class=&quot;user-hover&quot; rel=&quot;5e17508d5361330daaeb6d63&quot; data-account-id=&quot;5e17508d5361330daaeb6d63&quot; accountid=&quot;5e17508d5361330daaeb6d63&quot; rel=&quot;noreferrer&quot;&gt;Istv&#225;n Bender&lt;/a&gt;, I&apos;m hoping you can provide some assistance with this one.  Is there a procedure for releasing this to npm-folio and npm-folioci for our platform builds?  Please correct me if any of my assumptions in the description about needing to pre-transpile this project are incorrect.&lt;/p&gt;</comment>
                                                            <comment id="192707" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Mon, 15 Oct 2018 19:08:35 +0000"  >&lt;p&gt;Looking at &lt;b&gt;folio/react-big-calendar&lt;/b&gt;, it seems we need some combination of &lt;b&gt;build&lt;/b&gt; and/or &lt;b&gt;release&lt;/b&gt; package scripts to get this done.&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;&quot;build&quot;: &quot;yarn run clean &amp;amp;&amp;amp; babel src --out-dir lib &amp;amp;&amp;amp; yarn run assets &amp;amp;&amp;amp; yarn run less&quot;,
&quot;release&quot;: &quot;release&quot;,
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Running the &lt;b&gt;build&lt;/b&gt; script generates a whole &lt;b&gt;/lib&lt;/b&gt; of transpiled content. Looking at existing published artifacts, there is no lib folder because our Jenkins isn&apos;t running &lt;b&gt;build&lt;/b&gt;.  &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5f9abc1eb45b2e007453f423&quot; class=&quot;user-hover&quot; rel=&quot;5f9abc1eb45b2e007453f423&quot; data-account-id=&quot;5f9abc1eb45b2e007453f423&quot; accountid=&quot;5f9abc1eb45b2e007453f423&quot; rel=&quot;noreferrer&quot;&gt;John Malconian&lt;/a&gt; notes that we could use our &lt;b&gt;Jenkinsfile&lt;/b&gt; to invoke other scripts in addition to our normal CI routine.&lt;/p&gt;
&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;runScripts = [
   &apos;build&apos;
]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;Even with the /lib directory, the package.json &lt;b&gt;main&lt;/b&gt; points to /src/index.js which is not transpiled.  Interestingly the &lt;b&gt;files&lt;/b&gt; array of package.json references /src and /lib/css (but not /lib).&lt;/p&gt;

&lt;div class=&quot;preformatted panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;preformattedContent panelContent&quot;&gt;
&lt;pre&gt;  &quot;files&quot;: [
    &quot;src/&quot;,
    &quot;lib/css&quot;,
    &quot;LICENSE&quot;,
    &quot;README.md&quot;,
    &quot;CHANGELOG.md&quot;
  ]
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;&lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5e17508d5361330daaeb6d63&quot; class=&quot;user-hover&quot; rel=&quot;5e17508d5361330daaeb6d63&quot; data-account-id=&quot;5e17508d5361330daaeb6d63&quot; accountid=&quot;5e17508d5361330daaeb6d63&quot; rel=&quot;noreferrer&quot;&gt;Istv&#225;n Bender&lt;/a&gt; can please you comment?  It appears you prepared the previous release.  I&apos;m curious what your steps were.&lt;/p&gt;

&lt;p&gt;&lt;b&gt;Open questions:&lt;/b&gt;&lt;br/&gt;
(1) What build artifacts do we need to publish for &lt;b&gt;folio/react-big-calendar&lt;/b&gt;?&lt;br/&gt;
(2) Do we need to transpile &lt;b&gt;folio/react-big-calendar&lt;/b&gt; when building a platform?&lt;/p&gt;

&lt;p&gt;If the answer to the second question is yes, then we would have to account for this project&apos;s &lt;b&gt;.babelrc&lt;/b&gt; configuration during our build. If the answer is no, then we simply add this to our folio-scope exclusions.  I&apos;d prefer to rely on the transpiled artifacts if possible.&lt;/p&gt;</comment>
                                                            <comment id="192712" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Mon, 15 Oct 2018 19:27:56 +0000"  >&lt;p&gt;Also in chatting with &lt;a href=&quot;https://folio-org.atlassian.net/secure/ViewProfile.jspa?accountId=5cd595118fa24d0dd2de1253&quot; class=&quot;user-hover&quot; rel=&quot;5cd595118fa24d0dd2de1253&quot; data-account-id=&quot;5cd595118fa24d0dd2de1253&quot; accountid=&quot;5cd595118fa24d0dd2de1253&quot; rel=&quot;noreferrer&quot;&gt;John Coburn&lt;/a&gt;, this may represent a more general issue in that any forked repo could come with its own build and publish steps. Ideally we have a way to instruct Jenkins on this and &lt;b&gt;runScripts&lt;/b&gt; is probably the solution.  A document/guide/recommendation on what to review when introducing a third-party fork into our CI would help.  Created 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;STRIPES-570&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/STRIPES-570&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Document handling of forked repos in Stripes build&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            STRIPES-570
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
&lt;/p&gt;</comment>
                                                            <comment id="192715" author="557058:624212b9-5938-4e3b-84c6-8c8a8db84996" created="Mon, 22 Oct 2018 19:16:12 +0000"  >&lt;p&gt;I&apos;m marking this complete with respect to identifying a solution with runScripts, finding the publishing changes in the upstream repo, and including folio/react-big-calendar in the exclusion list preventing it from being transpiled during the webpack build (&lt;a href=&quot;https://github.com/folio-org/stripes-core/pull/468&quot; class=&quot;external-link&quot; rel=&quot;nofollow noreferrer&quot;&gt;https://github.com/folio-org/stripes-core/pull/468&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;However, there still is work remaining to merge the latest upstream changes into folio/react-big-calendar so the transpiled code is properly generated and referenced.  This is outlined in 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;UICAL-46&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/UICAL-46&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Update folio/react-big-calendar&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            UICAL-46
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
 and continues to block 
    &lt;span class=&quot;jira-issue-macro resolved&quot; data-jira-key=&quot;FOLIO-1549&quot; &gt;
                &lt;a href=&quot;https://folio-org.atlassian.net/browse/FOLIO-1549&quot; class=&quot;jira-issue-macro-key issue-link&quot;  title=&quot;Upgrade platform-complete to stripes 1.0&quot; &gt;
            &lt;img class=&quot;icon&quot; src=&quot;https://folio-org.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10318?size=medium&quot; /&gt;
            FOLIO-1549
        &lt;/a&gt;
                                                    &lt;span class=&quot;aui-lozenge aui-lozenge-subtle aui-lozenge-success jira-macro-single-issue-export-pdf&quot;&gt;Closed&lt;/span&gt;
            &lt;/span&gt;
.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="80887">FOLIO-1549</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="61368">STRIPES-570</issuekey>
        </issuelink>
                            </outwardlinks>
                                                                <inwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="70140">UICAL-46</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10019" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|hzz1pz:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10020" key="com.pyxis.greenhopper.jira:gh-sprint">
                        <customfieldname>Sprint</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10025" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>[CHART] Time in Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>