-
-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
ci(): switch the old custom build for rollup #8013
Conversation
Code Coverage Summary
|
Code Coverage Summary
|
ok browser import is broken |
Code Coverage Summary
|
i m trying to add rollup without changing much else. |
Code Coverage Summary
|
Code Coverage Summary
|
i ll make a branch from here to test partial swapping of a single file or function to a different export method. But seems to work. |
Code Coverage Summary
|
I have tested the new build. |
in a different branch i will convert a single function of the misc utils to TS, and see if that + ts + rollup-ts-whatever works |
I checked the old build size with and without svg and found
Is it a big enough difference to support svg as an opt in or can it be built in? |
In theory we can move all the svg related functions in a different file and developers will import them when needed. of course 16kb is not that big, but if you are not doing anything with svg import and export, maybe you don't want to load that code anyway. When everything is on import/export it should be very easy to do tests. |
Code Coverage Summary
|
Code Coverage Summary
|
Code Coverage Summary
|
Code Coverage Summary
|
Code Coverage Summary
|
1 similar comment
Code Coverage Summary
|
ok now the PR is green, i won't touch it. |
I gave a look at my open PRs and I marked 3 huge ones: |
I re read the draggable text pr, and while i m sure is a good feature we want to add, i currently don't like how we attach it to the events, i would like to write down all the pr is doing and see if we can break the code differently. Let me look the promises pr and let's get that in, then let's scehdule some time for the draggable text after i m sure i can expose my point of view and comunicate it properly. |
Code Coverage Summary
|
Code Coverage Summary
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
@@ -105,7 +105,6 @@ | |||
*/ | |||
QUnit.assert.sameImageObject = function (actual, expected) { | |||
var a = {}, b = {}; | |||
expected = expected || REFERENCE_IMG_OBJECT; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
?
@@ -889,7 +889,7 @@ | |||
|
|||
group1.addRelativeToGroup(rect5); | |||
var t = group1.calcTransformMatrix(); | |||
var pos = fabric.util.transformPoint(new fabric.Point(rect5.left, rect5.top), t); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess I wanted to check something here and didn't complete
@@ -35,7 +36,7 @@ | |||
var parseEl = fabric.document.createElement('div'), | |||
supportsOpacity = typeof parseEl.style.opacity === 'string', | |||
supportsFilters = typeof parseEl.style.filter === 'string', | |||
reOpacity = /alpha\s*\(\s*opacity\s*=\s*([^\)]+)\)/, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you sure about this?
@@ -0,0 +1,11 @@ | |||
interface NominalTag<T> { | |||
'nominalTag': T; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'nominalTag': T; | |
'nominalTag'?: T; |
This test works, but while the code changes seems large and aren't ( all whitespace and mandatory function wrapping ),
this change itself doesn't give us much.
I made this to have a small step transition that could allow tracing back issues to particular commits, and i would like the classes to transition one at one to be able to use git commit meaningfully.
If from this point modules can be migrated one by one ( starting from leaf nodes going up to the basic one ) ok then we can merge it, otherwise is pointless.
I ll experiment more and check
To look at PR:
https://github.com/fabricjs/fabric.js/pull/8013/files?diff=unified&w=1
most of the files will have changes like this.