You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm centralizing everything here so we can track it better.
I just went through and cleaned up the remaining PHPStan errors.
This is what's left, in order or highest priority to lowest:
Mobile placeholder outlines are too big
Authors who have only placeholder works end up at a 404. For example The Maltese Falcon works but Dashiell Hammet 404s. We should return a page listing all the placeholders.
Quick fix: In the EbookPlaceholderForm.php template, there are several <fieldset>s that only have a single child <label>. We should restructure that to remove those <fieldset>s as that doesn't make semantic sense. For example line 79, line 105, line 130 etc.
Add a dropdown to specify series type for collections when adding a new placeholder
Form to update placeholders
Form to delete placeholders (this has already occurred, a placeholder for a short story was added by mistake)
Update the wanted list to use placeholders from DB
When we release an ebook that deletes a placeholder, what happens if the collection info for the actual ebook differs from the placeholder's collection info?
Fixing remaining PHPStan errors
The text was updated successfully, but these errors were encountered:
Thanks for the prioritized list and all your recent fixes, too!
I'm going to mark this one as fixed:
When we release an ebook that deletes a placeholder, what happens if the collection info for the actual ebook differs from the placeholder's collection info?
These two lines in Ebook::Save() do the right thing:
I'm centralizing everything here so we can track it better.
I just went through and cleaned up the remaining PHPStan errors.
This is what's left, in order or highest priority to lowest:
<fieldset>
s that only have a single child<label>
. We should restructure that to remove those<fieldset>
s as that doesn't make semantic sense. For example line 79, line 105, line 130 etc.The text was updated successfully, but these errors were encountered: