astro-reactive-library VS astro-reactive

I was recommended to take a look at this project called the Astro Reactive Library. This repository builds components and architecture for projects that use the Astro framework for their reactive user interfaces.

generate a favicon.ico for our apps This issue looks to update the favicon logo to match the current logo that they are using. My PR.

I completed my work on issue #201 and PR #224 for that issue. The PR was eventually merged into the main branch after a couple of necessary adjustments. I ended up having to adjust the querySelector in order to remove a condition. The querySelector now only selects elements with the attribute data-validation-on. This allowed me to simplify the code while only selecting elements from the page that were created by the library. Furthermore, I had to add a nullish operator to set the default event listener if there is no attribute specifying one. I also added optional chaining to check whether the attribute actually exists, to avoid any errors.

First, I tackled the issue here. This issue looks to update the favicon logo to match the current logo that they are using. To do this, I used the .svg logo they had and generated a favicon.ico with it. I created a pull request and had some feedback about it. I had only tested it visually using light mode and had not considered how it would look using dark mode. On dark mode, the icon had bad contrast since the it was dark blue on a dark grey background. So to fix this, I added a circular white background to the logo so that it would look good on both light and dark mode.

I began my work on issue #201. I was initially confused by the the description of the feature to be implemented, so I asked the project maintainer to explain it further. Another project contributor also further explained what was needed and this really helped me out. I also read up further on the Astro framework to understand how the project is put together. I started with the documentation explaining how Astro components work and read on from there.

This week I have chosen to work on the Astro Reactive Library repo for release 0.4. I chose this repo because I have been contributing to it for the last couple of months and I am familiar with the project. I will be working on two issues:

I chose to work on 2 or more smaller but related issues. The issues I chose were from a project that I've previously worked on called Astro Reactive Library. This project builds components and architecture for other projects that use the Astro framework for their reactive user interfaces.

So after this learning process I felt comfortable looking at issues and determining which one I could tackle. I took a look at issue #140 which was related to the components used to create forms. To summarize, the way they assigned the id attribute of the tag the same value as the name. However, the project owner believed that this would cause issues since they use IDs as selectors, so the id attribute needs to be unique. The ideal solution was to create an id attribute that is not the same as the name attribute by making a function that creates a Short Unique ID (UUID). The UUID should be prefixed with arl and assigned that as the id value for every tag.

The issue was to add a setValue method to the FormGroup class. This would allow anyone using Astro to set the values of any form controls in that form group. For example:

This week I completed my final Hacktoberfest PR. For my final PR, I chose to contribute to Astro reactive library. Astro reactive library uses the Astro framework to let you build reactive user interfaces.