- Add try-catch block to handle null response from API
- Log errors and return appropriate HTTP responses
- Update error message in 503.blade.php to show exception message if available
- Changed method name from support to donate in HomeController
- Updated footer link and view references from support to donate
- Renamed support.blade.php to donate.blade.php for consistency
- Updated route endpoint from /support-me to /donate in web.php
- Integrate LMI API to fetch current sales data using the provided API key.
- Update SaleController to use Http facade for making API requests.
- Modify services configuration to include LMI API key.
- Refactored the `getSkinImageAttribute` method in ChampionSkin model to accept a boolean parameter for uncentered images.
- Updated references to `getSkinImageAttribute` in ChampionSkinController and blade files to include the new parameter for uncentered images.
- Updated the Champion model to include an optional parameter for retrieving uncentered champion images. Adjusted image URLs in relevant views accordingly.
- Refactored the code in `PostsController.php` to filter out hidden posts before sorting by date for better performance and accuracy.
- Updated the blade template `listposts.blade.php` to adjust formatting and structure for displaying posts.
- Added a new method `roadmap` to HomeController for displaying the roadmap view.
- Created a new Blade template `roadmap.blade.php` for the roadmap page.
- Defined a route `/roadmap` to access the roadmap feature.
- Added caching mechanism to store and retrieve streamer data for API responses, improving performance.
- Implemented cache forget method in StreamerPanelController for CRUD operations to update cached data accordingly.
- Added Champion model to StreamerPanelController.
- Implemented form validation for champion_id, platform, username, and displayname in create and update methods.
- Created StreamerCreateForm and StreamersTable components for better organization.
- Added StreamerController with index and show methods
- Added StreamerPanelController with index, create, store, edit, update, and destroy methods
- Created Streamer model with fillable attributes and platform-specific URL generation logic
- Implemented migration for creating the streamers table
- Added hCaptcha validation to the contact form.
- Integrated hCaptcha configuration in the application.
- Implemented Discord alerts for new contact submissions with detailed content.
- Added ContactSubmissionController with index and store methods for handling contact submissions.
- Created a new Blade view for the contact form with fields for name, email, discord, category, subject, and message.
- Updated routes to include endpoints for displaying the contact form and submitting it.
- Updated the query in HomeController@index to filter upcoming skins based on release date.
- Updated the query in HomeController@index to filter latest skins based on release date.
- Added links to champion details page for each champion in list_all.blade.php.
- Added links to skin details page for each skin in recent_skins.blade.php and upcoming_skins.blade.php.
- Update the cache expiration time for 'championsListAllCache' and 'championsRolesCache' to 8 hours.
- Update the cache expiration time for 'championShowCache{slug}' to 3 days.
- Update the cache expiration time for 'championSplashColorCache{slug}' to 6 months.
- Update the cache expiration time for 'championSkinShowCache{slug}' to 48 hours.
- Update the cache expiration time for 'championSkinSplashColorCache{slug}' to 120 hours.
- Refactored the ChampionController, ChampionSkinController, HomeController, SaleController, SummonerEmoteController, and SummonerIconController to use arrow functions for cache callbacks.
- Updated the view data passing in the ChampionController, ChampionSkinController, HomeController, PostsController, SaleController, SummonerEmoteController, and SummonerIconController to use associative arrays instead of compact().
- Removed unused imports from web.php.
This commit adds pagination functionality to the posts index page. The code changes include:
- Sorting the posts by descending date
- Paginating the posts with 6 items per page
- Creating a new component called "Listposts" for rendering the paginated posts
- Adding a new view file for the "Listposts" component
- Updating the blade template of the posts index page to use the "Listposts" component and pass in the paginated posts
The purpose of these changes is to improve user experience by displaying a limited number of posts per page and providing navigation links for easier browsing.
- Added a new file `PostsController.php` in the `app/Http/Controllers` directory.
- Implemented the `index()` method to retrieve all posts using the Sheets facade.
- Implemented the `show()` method to display a single post using route model binding with Sheets.
- Updated the `RouteServiceProvider.php` file to bind the 'post' route parameter to retrieve posts from the Sheets collection.
- Created a new configuration file `sheets.php` in the `config` directory, defining default settings for collections and their corresponding sheet classes, path parsers, content parsers, and extensions.
- Added a new markdown file `hello-world.md` in the `content/posts` directory as an example post.
- Created two new blade view files: `index.blade.php` and `show.blade.php`, under the `resources/views/posts` directory, for displaying lists of posts and individual post details respectively.
- Modified the existing web routes (`web.php`) to include routes for accessing posts.
The changes enable users to view all posts on `/posts`, as well as access individual post details at `/post/{post}`.
* feat(controllers): add AboutController and FAQController
- Added new controllers for the About page and FAQ page.
- The AboutController handles requests related to the About page.
- The FAQController handles requests related to the FAQ page.
feat(components): add Dropdown component
- Created a new Dropdown component for displaying questions and answers in the FAQ page.
- The Dropdown component takes in a question and answer as props.
feat(views): add blade templates for Heimerdinger and League of Legends FAQs
- Added blade templates for displaying frequently asked questions about Heimerdinger and League of Legends.
- The Heimerdinger template includes specific questions and answers about Heimerdinger, along with relevant meta tags for SEO purposes.
- The League of Legends template includes general questions and answers about League of Legends, along with relevant meta tags.
* feat(faq): add Heimerdinger's backstory and naming
- Added a new FAQ dropdown for Heimerdinger's backstory, providing information about his origins, role in Piltover, and association with Ekko.
- Included another FAQ dropdown that explains the inspiration behind Heimerdinger's name, combining J. Robert Oppenheimer and Erwin Schrödinger.
- These additions enhance the user's understanding of Heimerdinger's character and background.
* Apply fixes from StyleCI
* refactor(components): simplify constructor syntax
- Refactored the constructor syntax in the `Dropdown` component to use a simplified format.
- Removed unnecessary line breaks and indentation for improved readability.
* refactor(faq): update Heimerdinger page layout
- Change the heading tag from `<h2>` to `<h1>` for better semantic structure.
- Update the paragraph tag from `<p>` to `<h2>` for consistency with other sections.
- Improve the readability and maintainability of the code.
* feat(controllers): add AboutController and FAQController
- Added new controllers for the About page and FAQ page.
- The AboutController handles requests related to the About page.
- The FAQController handles requests related to the FAQ page.
feat(components): add Dropdown component
- Created a new Dropdown component for displaying questions and answers in the FAQ page.
- The Dropdown component takes in a question and answer as props.
feat(views): add blade templates for Heimerdinger and League of Legends FAQs
- Added blade templates for displaying frequently asked questions about Heimerdinger and League of Legends.
- The Heimerdinger template includes specific questions and answers about Heimerdinger, along with relevant meta tags for SEO purposes.
- The League of Legends template includes general questions and answers about League of Legends, along with relevant meta tags.
* feat(faq): add Heimerdinger's backstory and naming
- Added a new FAQ dropdown for Heimerdinger's backstory, providing information about his origins, role in Piltover, and association with Ekko.
- Included another FAQ dropdown that explains the inspiration behind Heimerdinger's name, combining J. Robert Oppenheimer and Erwin Schrödinger.
- These additions enhance the user's understanding of Heimerdinger's character and background.
* Apply fixes from StyleCI
* refactor(components): simplify constructor syntax
- Refactored the constructor syntax in the `Dropdown` component to use a simplified format.
- Removed unnecessary line breaks and indentation for improved readability.
* refactor(faq): update Heimerdinger page layout
- Change the heading tag from `<h2>` to `<h1>` for better semantic structure.
- Update the paragraph tag from `<p>` to `<h2>` for consistency with other sections.
- Improve the readability and maintainability of the code.
* feat(about): add about page and route
- Added a new AboutController class with an index method to handle the /about route.
- Created a new blade template file, index.blade.php, for the about page.
- Added HTML markup and content for the about page.
- Updated web.php routes file to include the /about route.
* feat(about): add information about League of Legends, Heimerdinger
- Added a section with detailed information about League of Legends, including its gameplay, competitive scene, and spin-off game modes.
- Included a section introducing Heimerdinger.lol as a fan-made website dedicated to providing information about League of Legends.
- Added a section describing the character Heimerdinger, his role in the game, and his appearance in the animated series Arcane.
* feat(navbar): update About link and fix routing issue
- Updated the href attribute of the About link in the navbar component to point to the correct route.
- Fixed a routing issue where the active class was not being applied correctly when on the About page.
---------
Co-authored-by: Rico <rico-vz@users.noreply.github.com>
- Added a new file `SaleController.php` in the `app/Http/Controllers` directory to handle sales-related logic.
- Created a new file `Current_sales.php` in the `app/View/Components/Sales` directory to define the `Current_sales` component.
- Added a new file `current_sales.blade.php` in the `resources/views/components/sales` directory to display the current sales.
- Modified the `web.php` routes file to include a route for accessing the sales page.
These changes introduce functionality related to displaying and managing sales data on the website.
