-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Update to Font Awesome 5 (Develop) #957
Conversation
…n FA5) Apply fix to AdminLTE to work with FA5
Codecov Report
@@ Coverage Diff @@
## develop #957 +/- ##
===========================================
+ Coverage 66.96% 67% +0.03%
- Complexity 1918 1921 +3
===========================================
Files 160 161 +1
Lines 6693 6700 +7
===========================================
+ Hits 4482 4489 +7
Misses 2211 2211
Continue to review full report at Codecov.
|
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.
Few things here that will need to addressed from what I can see, also this will be a breaking change so release wise it'll be most likely part of 4.3.
Definitively something for |
{ | ||
if ($this->schema->hasTable('groups')) { | ||
$this->schema->table('groups', function (Blueprint $table) { | ||
$table->string('icon', 100)->default('NULL')->change(); |
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.
Should it be null, or an empty string? 🤔
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 went with NULL based off this post: https://stackoverflow.com/questions/38351498/remove-default-in-migration
I also compared to the other columns in the table that did not have a default set when the migration ran, and they all showed NULL
for the Default
property. In mysql here is how the results of my testing:
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.
Should be possible to do an export of the create table logic to see if the default value was truly reversed (the cleaner the better, leftovers attract edge cases).
Assuming I remember, I'll take a look at what the DDL ends up being.
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.
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 think the posted DDL is wrong. Or its mislabeled? I'll still have to look at this myself, but it works as a good reminder none-the-less, so thanks.
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 am curious about what is wrong?
Other than ('fas fa-user')
in this line, the down method returns the table to the 'original' state. I was not certain how to handle this but I thought it would be better to set the default to use the new fas
convention rather than the fa
.
I relabeled my pictures above that might help clear up any confusion.
@Silic0nS0ldier What can I do to help make this review easier for you? Also, if it will help simplify things I can move the bakery command into a new branch and out of this PR. |
@amosfolz My main limitation at the moment is time, or more specifically whenever I have free time there is something jumping up and down screaming for my attention. There isn't much that can be done about that in the meantime unfortunately, however I will get to this (eventually). One thing that would help however is if you could note that a given PR is ready for review. If I see added commits without a message once the work is done, I'll just end up assuming that isn't in a ready for final review state. |
This is ready for review! :-) |
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.
Found two places where the icons are missing :
I also get this error. Might be a conflict from the AdminLTE update?
[Error] SyntaxError: Unexpected token ';'. Expected ')' to end an argument list.
(fonction anonyme) (AdminLTE.js:687)
[Error] TypeError: undefined is not an object (evaluating '$.AdminLTE')
Code général (AdminLTE-custom.js:24)
And pro doesn't work :(
app/sprinkles/account/src/Database/Migrations/v430/UpdateGroupsTable.php
Outdated
Show resolved
Hide resolved
Looks like |
Change to font awesome to version 5.9
update fa-trash-alt to fa-trash-o and fa-gear to fa-cog
Not sure what happened with Also needed to fix the following two icons:
|
Just leaving a note for myself if/when I come back to try to add in the bakery command... |
FA Pro is probably something we can live with having only a guide in the doc on how to do it in your sprinkle. |
Most of the changes are simply updating the 'fa' tag to the new 'fas' convention.
I do not have a Font Awesome 5 Pro subscription so the bakery command still requires some testing.
#870